Protected workflow triggers
Enterprise customers can now use Source Control to protect workflow triggers. This prevents changes to a workflow's triggers without review. When you protect a workflow for the first time, triggers are now automatically included.
To enable protected workflow triggers for self-hosted Retool on the stable channel, reach out to your Account Manager to enable the Allow users to edit triggers on branches feature flag.
For workflows that are already protected, you now have the option to protect triggers using a new PR.
Once protected, triggers are versioned and published alongside each release. Information about your triggers is stored in the startTrigger.yml file in your Source Control repository.