as I learned there is a limit of maximum 10.000 actions per flow:
This is every block/action which can be executed in a task/menu and not only a Data Action call or so.
I face an issue with that limit when we build a helper inbound flow. This flow is executed and has two nested loops and run over all entried of a Data Table (entried are fetched by Data action and paging).
Every entry is checked in flow for some actual date stuff and sometimes we have to delete a entry by Data Action or not.
During that execution in the last time I always reached that maximum flow action limit. This was confirmed by Customer Care.
My question is if I can avoid that limit when I use the "Transfer to flow" action and transfer all the time to the same flow again to save the external loop. Does this transfer to flow and the new beginning of the flow always decrease that limit counter again to 0?
Hi @ciwe
Breaking the operations into chunks and recycling into the flow until they're all processed sounds like one way to address your issue.
Another option would be to move the process to an external server outside of the Architect flow, then use a custom web data action in the flow to invoke the process there, where the limits wont apply.
yes I made it like this as you wrote with first possibility.
I recycle one loop and rebuild the flow so that it call itself and steer this with participant datas.
It is working now and I don't reach that limit anymore. On the other hand is made my flow really complex and don't know if any other could understand what I built there...
By the way does anybody knows when it is possible to read the Archtect flow execution logs myself without to ask Genesys all the time?