Skip to content

Incident detail

Unable to save Phone Numbers with Studio Flow

Resolved incidentMinor

Timeline window

to

Outage alerts

Get alerted the next time Twilio breaks

Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Investigating

    Our monitoring systems have detected a potential issue with saving phone numbers in studio flow. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

  2. Investigating

    Our engineers are investigating the issue causing generic errors when saving phone number configurations assigned to a Studio Flow in the Console, and are actively working to deploy a fix. As a temporary workaround, please ensure a valid Status Callback URL is populated when setting your Voice URL to a Studio Flow. We expect to provide another update in 1 hour or as soon as more information becomes available

  3. Investigating

    Our engineers continue to investigate the issue causing generic errors when saving phone number configurations assigned to a Studio Flow in the Console, and are actively working to deploy a fix. As a temporary workaround, please ensure a valid Status Callback URL is populated when setting your Voice URL to a Studio Flow. We expect to provide another update in 2 hour or as soon as more information becomes available

  4. Monitoring

    The issue causing generic errors when saving phone number configurations assigned to a Studio Flow in the Console are now operating normally. We will continue to monitor for system stability. We'll provide another update in 2 hours or as soon as more information becomes available.

  5. Resolved

    We are no longer experiencing generic errors when saving phone number configurations assigned to a Studio Flow in the Console. This incident has been resolved.