For the purpose of being able to “verify” or “wait for condition X” that all actions from a previous workflow or previous steps are completed, I would love to see the possiblity to add a Delay in non-user-interaction workflows.
Basically the same functionality that already exists in the user-interaction workflows, but then expanded to the other workflows.
Background:
I have workflow 1 creating a couple rows in a helper table. end of the workflow, I trigger workflow 2 to process those rows and create Google Calendar appointments from it. However, workflow 2 sometimes doesn’t process anything as it provides the following feedback: “No data for this trigger” (something along those lines). When manually activating the workflow using a button afterwards or re-running it using whatever trigger, everything gets processed properly. Probably even a 1s delay could fix this issue for me (and others I’ve heard @ThinhDinh :D).
Can I assume that your Helper table is a regular Glide Table?
If it is, try switching it for a Glide Big table. You might find that resolves the issue.
@Darren_Murphy Thanks for your suggestion! Respectfully, may I ask, can you explain to me how that might resolve the issue? It requires rebuilding quite some things, so it would be helpful to know whether that will resolve the issue.
What I’ve done right now as a workaround: I added a dummy Query step in the workflow, which takes up to 3s. Not using any of the Queried data, but I’m hoping that might resolve the issue.
That should resolve the issue because when writing into Big Tables, workflows proceed to the next step after the update is in the database. This is not the case with regular tables, where workflows would go to the following steps when the updated was queued (meaning it’s not guaranteed to have reached the database at the moment of triggering the next workflow step)
@tuzin thanks for the explanation! What about the speed of the Big Table? Do you expect the entire flow to take a lot more time or will this be near-to-instant? (using roughly 25 columns, up to 3 rows per loop, no query or rollup functions)
Looping in workflows is relatively slow with any data source. From my perspective, Big Tables are fast, but you would have to test and see if it matches your expectations
