In the company I work for, we've been making software using retool workflows. Of course, this type of software have breaking changes so we test it using different environments. Currently, we have staging and productions env's enabled at retool.
The thing is our workflows communicate with each other, and before we did it using simple REST query's blocks, using environment as a queryparam on the workflow route.
The thing is that sometimes this type of requests get throttled or the request just times out, so we want a better way to do it. We saw this new query blocks that executes workflows:
But this doesn't work because it always executes the next workflow on production, even when we execute the first one on staging.
Are we doing something wrong or this is not the expected behaviour, or maybe it's a bug?
Hey folks! Thanks for reporting this. It looks likely that this is a bug on our end, or a feature that was missed in the overlap between workflows blocks and environments. We have been able to reproduce the issue, have brought it to the dev team, and can let you know here when it's resolved.
In the meantime, triggering the webhook via a REST resource may be the best way to go. Are there particular instances where you're currently running into throttling issues?
Hey @Mitchel_Jimenez and @CWhite the behavior of this should be fixed in 3.10 so that workflows are run in the same environment as the app/workflow that triggers them. Let me know if you're still having issues!
