Ari Sosnovsky

@anuragphadnis I agree with this line of thinking. In my case I had a networking issue that restricted the db from being reachable by my cluster. The issue was hard...

@anuragphadnis i don't mind taking this to completion. If your change is already merged, I can do the rest of the work and update the checkdb command :)

Thanks for reporting this. I will try to get to this in the next round of UI updates!

Take a look at the new release v0.6.1

Sorry it took me so long to reply, long week. So this looks like possibly one of your automatons is not valid. Can you: 1. Share the automation you tried...

ok, so it sounds like I need to implement a better error handle for when an invalid automation (according to shortumation) is loaded.

@isewise Take a look at the new release v0.6.1

@martkopecky split config support is now in v0.6+

> Unfortunately, even the new version does not work for me... > > > >  > > > > The automation is stored in config\packages\automations\cover.yaml > > ``` >...

@martkopecky packages support is now up to date with v0.6.3! :)