For now we don't have a UI to acitvate / deactivate FlowRuns specifically. The only way to do this is 'all or nothing', this means when a flow is active / not active then all its flowRuns are active too and vice versa.
This leads to unexpected behavior for the user. For example if the user creates a lot of flowRuns for a scheduled flow, then he gets tasks from every flowRun but he only 'sees' the latest flowRun in the frontend and the user cannot see where they come from exactly.
[x] deactivate all old flows when deploying a new flowRun
[x] only update the active state from the latest flowRun when updating the active state of the flow
johipsum
commented
6 years ago
For now we don't have a UI to acitvate / deactivate FlowRuns specifically. The only way to do this is 'all or nothing', this means when a flow is active / not active then all its flowRuns are active too and vice versa.
This leads to unexpected behavior for the user. For example if the user creates a lot of flowRuns for a scheduled flow, then he gets tasks from every flowRun but he only 'sees' the latest flowRun in the frontend and the user cannot see where they come from exactly.