A separate flow type, to stop other flows.
This feature being implemented as an actual flow, would allow to manage connectivity between flows, in more complex scenarios. Currently, the same behaviour is achieveable with internal API usage, however this leads to ambiguous flows, as they only contain the ID's, rather than a concrete relation to the flow. If this was implemented as a separate flow, the "Find Usage" button will also show the relation, to avoid any problems of that kind.
As an example for how this type of flow can be used. It would be possible, to set up automatic maintenance windows for CDC patterns (scheduled stopping). Or in scheduled nested flows, rather than setting a rule, that X flow can not be running, when starting the schedule, the schedule will start a nested flow that stops the X flow, if it is already running.
Ideally, the flow would allow you to select other flows from a dropdown, and should wait for the specific flow to actually be stopped, rather than cancelled with running tasks.
Comments: 2
-
13 Feb
Olena Sherbinin AdminTake a look at suspend (and unsuspend) API endpoints: https://support.etlworks.com/hc/en-us/articles/360035985034-Flows-management-API#SuspendFlowexecutions
-
14 Feb
Heiko ParmasAPI endpoints are a viable workaround for the action of stopping a flow, but would not solve the problem of not show up in showing where a flow is referenced by other flows.
I would also like to add, that it would be nice if the stopping of flows actually waited until all tasks are finished, before returning.