For the past 9 months I have used a Bot that is acting on a parent row initiated by an edit, this Bot creates rows in another table. It then updates a status column in the parent row to trigger another Bot listening for that change.
The reason for this, is the webhook I use in the second Bot needs to see the records created by the first Bot.
Up untill a few days ago this worked fine. But my start expressions in my webhook on the second Bot no longer see the new records created by the initial Bot. No changes to performance settings or formulas related to the Bots.
Anyone else having a similar issue?
1 Like
To address the issue concisely:
1. Add a Delay:
- Introduce a wait step in the first bot after it creates rows in another table. For example, add a 5-10 second delay before updating the status column in the parent row.
2. Intermediate Status Column:
- Create an intermediate status (e.g., “Processing”) that the first bot sets after creating rows.
- Set the second bot to trigger when the status changes to “Completed.”
3. Reconfigure Bot Triggers:
- Ensure the second bot is configured to trigger specifically when the status column changes to ensure the first bot’s actions are completed.
Steps:
- First Bot
- Trigger: On parent row edit.
- Actions: Create rows in another table, wait for 5 seconds, update status to “Processing.”
- Second Bot:
- Trigger: When status changes to “Completed.”
- Actions: Execute the webhook.
This setup ensures that the second bot only triggers after the first bot has completed its actions.
The wait time implementation sounds logical, however i dont think i can do anything under 5 minutes for the built in wait step. Even if i was to make it a conditional step based on the rows existing.
I have turned on the return value for the “Create Rows” Webhook which seems to have fixed my problem, I am not doing anything with the return value and i should state that the asynchronous option has also always been OFF, but it seems to ensure it doesnt update the status column prematurely.
1 Like