Objective
This article shows you how to publish a Studio flow so the changes you have saved as a draft become the version that handles live calls and messages, and how to read the errors that can stop a publish.
Product
Studio
Environment
Twilio Console
User Account Permission/Role(s) Required
Publishing requires the Studio flows create and update permissions on the account. With read-only access the Publish button is not shown.
Procedure
- In the Twilio Console, select Orchestration in the left sidebar.
- Select Studio, then Flows.
- Select the flow you want to publish.
- Review your changes on the Editor tab, or on the Details tab if you edited the flow definition or flow settings.
- Select Publish.
- A Flow published successfully confirmation appears, and the new revision becomes the currently published flow.
Additional Information
- If the details form still has unsaved edits when you select Publish, a Save and Publish flow dialog appears with the message "Your flow details have unsaved changes. To publish the latest version, you must save these changes first." Select Save and publish to save and publish together.
- If the flow cannot be published, a The flow could not be published message lists what to fix. It can include:
- a prompt to enter valid JSON in the flow definition, with a link to the Details tab
- a count of widgets missing required configuration
- specific field errors
- Published flows are connected to your Twilio phone numbers and can be interacted with by customers. Any changes you make without publishing are saved as drafts and can only be tested by the numbers listed as test users.
- To confirm what is live, open the Revision History tab and check the Currently published flow card.
This content was generated by AI and reviewed, edited, and verified by a human.