When I understand it well, Indicum will start a new instance when the previous is not ended. Is it possible to limit the number of multiple running instances?
Solved
Is it possible to limit the number of multiple running instances for a system flow?
- Captain
Best answer by Erwin Ekkel
I don’t think this is possible by any settings. What you could do is create a counter table. In a decision node add +1 for that running instance and subtract 1 when finished in the last step. Then in the first step check if the counter is < 4 else stop that instance of the flow. This would prevent more then 3 running simultaneously.
- Rookie
Hi Andre,
There is a checkmark for systems flows in the process flow screen which is default off: multiple running instances
This should prevent indicium from starting another instance when the previous scheduled one is still running
- Captain
I don’t think this is possible by any settings. What you could do is create a counter table. In a decision node add +1 for that running instance and subtract 1 when finished in the last step. Then in the first step check if the counter is < 4 else stop that instance of the flow. This would prevent more then 3 running simultaneously.
- Captain
Feel free to create an idea for this in the ideas section.
What does this system flow functionally do? If it’s still running is the frequency correct? If it is started multiple times from API or user interactions perhaps it’s better to create a collector flow that runs every 5 minutes and groups these requests.
- Captain
The system flow processes new rows entered in a table. I want to protect the system being overloaded.
+5- Hero
Hi Andre,
Are the answers in this topic sufficient? If so, could you please select a “best answer”?
If you would like such a no-code solution, please follow the advice of Erwin and create an idea for this.
Best regards,
Nick Janssen
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.