We are building up an ever increasing catalogue of Workflows, and they all point off in this and that direction, doing their own thing!
Unfortunately, we have had a lot of Server issues this past few months, and links have changed, folders have moved, I.Ps have been updated.
It is driving me nuts in regard to deactivating, and reactivating the flows as a 'quick' way of checking their integrity.
Rather than hand turning off / on all of the flows we are using... is there an alternate way to deactivate all currently activated flows, AND THEN REACTIVATE. Or perhaps there is some sort of structure check that can be performed across all Flows?
Workflow Integrity Check
- TheCaptain
- Member
- Posts: 62
- Joined: Mon Jan 18, 2016 4:22 pm
- Location: London
Re: Workflow Integrity Check
I'd also like to know this. Switch has an administrator alert email but somehow there are times where things will unmount which do not trigger this email. The best way of checking that things are working is to stop and start all flows, we've found. So we end up just restarting our Switch Server every once in a while.
Chat: open-automation @ gitter
Code: open-automation & dominickp @ GitHub
Tools: Switch, Pitstop, EPMS, Veracore, PageDNA, SmartStream, Metrix
Code: open-automation & dominickp @ GitHub
Tools: Switch, Pitstop, EPMS, Veracore, PageDNA, SmartStream, Metrix
- TheCaptain
- Member
- Posts: 62
- Joined: Mon Jan 18, 2016 4:22 pm
- Location: London
Re: Workflow Integrity Check
I guess the workaround (to a certain degree), is to group associated Flows.
At least this way we end up with a smaller faction to reset.
As you say, the Notifications are helpful... but not exactly the answer we're looking for! Easiest route I've find is to wait for somebody to send an angry email! It's surprising how long some 'urgent' flows go unnoticed
At least this way we end up with a smaller faction to reset.
As you say, the Notifications are helpful... but not exactly the answer we're looking for! Easiest route I've find is to wait for somebody to send an angry email! It's surprising how long some 'urgent' flows go unnoticed
