I'm encountering an issue where my workflow is calling another workflow, but it's resulting in an error due to exceeding the rate limit for workflow invocations. I have two questions:
Is there a way to track how many workflows are currently running? This would allow me to wait for workflows to complete before calling another.
Are there any alternative solutions to manage this rate limit issue when invoking multiple workflows?
Any insights or best practices for handling this situation would be greatly appreciated
You can add two response components at the end of the flow: one for status 200 and another for status 400. To call another workflow, add a condition like this example: {{ workflow1.data.success === "Run Successfully" }}.
Hey @ZeroCodez
Yeah, I guess I could make batch calls to the workflow of 60 and wait for them to finish before calling the next batch. Thought that Retool would give some internal values to determine current usage to improve triggering of the workflows but if I need to just go the JS route I'll have to give a try. Thanks!
Hey @zach_b! Just to confirm, we currently expose metadata about the currently running workflow but very little, if anything, about other workflow runs in the same organization. I can talk to the team about potentially implementing something like that but I think using JS to batch your workflow triggers is probably the best path forward, for now!
