Release 5.3.37

What changed

This release focuses on Scenario Builder, more accurate broadcast routing, and overall system stability. Most changes are low-visibility in the interface, but they make day-to-day work more predictable.

After you remove a button from a scenario keyboard, linked transitions are rebuilt more reliably.
During scenario save and publish, the system behaves more clearly when something goes wrong.
Values in some Scenario Builder action settings are stored more accurately.
Broadcasts move to the next step more reliably when routing uses a named entry point.
Stability under load has been improved.

How it changed

Previously, removing a keyboard button could leave incorrect transitions, some publish errors created a rougher editing experience, and certain broadcast routes through named entry points could behave unpredictably.

Now, the builder updates transitions more accurately after button edits, completes the save flow more reliably or shows a clearer error, handles action-setting values more precisely, and routes broadcasts more confidently through the intended scenario step.

Why it matters: teams spend less time rechecking scenarios after edits, and important scenarios and broadcasts behave more predictably.