Hey everyone,
First off to @joeyg, we definitely recognize your point. We’ve experienced these issues before and have been brainstorming how we can better release new features without impacting apps in production. For instance, we’ve recently released a new experimental features panel as a move to de-risk releases. Nonetheless, in unusual situations, like this one, where we expect the feature to be a non-breaking add-on, we need to be more proactive about how we can comprehensively test and safely deploy – we’re scheduling a meeting next week with our team to discuss a few ideas.
On another note, as we’ve reached a point where the immediate release is as stable as it normally is, we’ve unpaused scheduled. We made this choice because otherwise, if you moved from immediate to scheduled, your app would retain the updated structure but be unable to understand it, meaning that it would assume all custom events and actions take in zero parameters and pass in zero parameters. This will now allow you to safely toggle on scheduled, if you wish to do so.