Retool onPrem 3.196.2
Single Instance with Staging and Production Resources configured.
How to Schedule a trigger of a protected workflow new branch for running whilst the main branch is running as scheduled trigger with production resource environment?
Let's assume I have a stable workflow running in Production Resources environment. I have to build a new version so I create a new branch, before merging it to main and deploy it I want to make it run for a while using Staging data source, and not just testing it with manual run.
ok I think this is a feature request because apparently only main branch is possible to be scheduled.
This is very restrictive especially if you have a single instance with multiple Resource Environments. The only way to test a major workflow change is to run it manually before merging to main
Same should be possible for webhooks.
The webhook or scheduled trigger deployment should be branch name + resource environment
Apologies for the inconvenience and thank you for reporting this
I just checked internally and it is an outstanding ticket for the workflows team, I can tag in this thread and your account which will definitely increate the weight and propriety for this!
I can also add in your suggestion for webhooks scheduled trigger
Added a +1 for this feature request and it is definitely on our roadmap.
I fully understand that you need to keep the running prod workflow up and currently this could be done if that prod workflow is unprotected but we are looking to add in parity for when the prod branch of the workflow is protected.
I will update this thread with any news I hear on the ticket
I'm not sure if the problem is strictly related to protected/unprotected workflows. As long as I can schedule a trigger on any branch is fine. E.g. I have the v1 on main and scheduled with production resources, I'm working on v2 and I want to test it with staging resources scheduling it, or production resources (e.g. a shadow prod)
I will make sure this feature request gets some attention from the team!
In the short term, a potential work around would be to use a separate space for triggering in-development workflows. Let me know if you would be open to that for your development cycle.
I know about the spaces, but it seems more appropriate to use them for different team rather than as environments, furthermore if I already have another team or more I will end up having teamA-staging teamA-prod teamB-staging teamB-prod etc etc.. is not practical.
