Retool Workflows Triggering in Different Environments

Hello,

I hope this finds you well. I'm currently facing an issue with my workflows in Retool and was hoping to get your advice.

I have set a trigger that starts at 7 AM local time and executes an API call with both development and production environments. The workflow is deployed with the trigger configured for the production environment. However, I assumed that in the development environment, it would automatically switch to the dev environment, but the API call continues to run in the production environment.

My question is: do I need two separate triggers—one for development and one for production—if I want the API call to execute for both environments? Or is there a more detailed explanation of how environments work in triggers? It seems the behavior differs from how environments function in apps or resources.

Any guidance on this would be greatly appreciated.

Thank you,

Valentina

Hi @valentina_campana, to run this WF on a schedule for both environments we would need two triggers. One for prod and one for dev:

Here is something to consider:

"When a workflow is calling another workflow, the child workflow will run in the same environment that the parent workflow is running in (which could be different from the environment the parent workflow was deployed in, for example if passing in a different environment in the webhook url)." - @kbn
-Source

thank you!

you are welcome! :slightly_smiling_face: