Twilio Studio flow rollback leaves execution state ambiguous

Flow Rollback and Execution State Clarity

When a Twilio Studio flow is rolled back to a previous version, new executions use the reverted definition while executions that started before the rollback continue with the version they were using at start.

The documentation does not specify whether flow‑level variables or execution state that were modified during the interim version are retained, cleared, or partially preserved for those ongoing executions after the rollback.

This ambiguity can affect downstream logic that depends on variable values or state shared across executions.

• Does the rollback preserve the current values of flow‑level variables for executions that are still running on the superseded version?
• If the reverted version does not define a variable that was added in the interim version, what happens to that variable’s value for the ongoing executions?
• Are any execution‑level state markers (such as widget‑level counters or timers) reset or kept when a flow is rolled back?