New Studio engine
Twilio is upgrading the execution engine that powers Studio flows. The new Studio engine is a rebuilt version of the infrastructure that runs your flows—designed to be more reliable, more secure, and better equipped to handle the workloads your business depends on.
New Studio accounts run on the new Studio engine. Existing accounts will be migrated gradually over the coming months. You don't need to do anything—Twilio manages this migration.
The original Studio engine has powered billions of flow executions since Studio launched. As Studio usage has grown and customer requirements have become more demanding, Twilio has outgrown it.
The new Studio engine has the following benefits over the classic engine:
- Reliability and resilience: The new Studio engine is designed so that an issue affecting a limited number of executions is contained and cannot cascade to others.
- Scale: The new Studio engine is built to handle certain kinds of high-volume, low-latency workloads that the classic engine was not designed for.
- Future capabilities: The new Studio engine is the foundation for new Studio capabilities that are not possible on the classic engine.
The new Studio engine runs the same Studio API, TwiML, flow definitions, and widgets your flows use today.
Twilio will migrate your flows to the new Studio engine automatically. You don't need to recreate flows, change any configuration, or take any action in the Studio console.
Your flows will continue to execute normally throughout the migration. The same Studio REST API, flow definitions, widget behavior, and execution semantics apply on the new Studio engine.
Twilio migrates accounts in phases. Within each phase, Twilio shifts traffic gradually with automated monitoring and rollback capability throughout.
Before each phase begins, Twilio runs a validation process to confirm that the new Studio engine handles real-world execution patterns identically to the classic engine. Migration proceeds only once that threshold is met.
To view which engine processed an execution, navigate to a flow's execution log in the Studio console and open any execution. The execution details view displays the engine—classic or new Studio engine—that processed it.
If you notice unexpected behavior in a flow execution during or after your migration window, contact Twilio Support with the execution SID. Twilio has tooling to identify which engine processed a given execution and can escalate to the engineering team if needed.