Twilio: Flex Dialpad Degradation Caused Stuck Tasks
Timeline of updates
- resolved
Flex Agents who attempted to create an Outbound Call from 1:49pm to 2:04pm PST may have Tasks that are stuck. Symptoms of this would be Flex Agents unable to change their Activity or being unable to receive Inbound Calls. However, Flex Agents would still be able to continue to place Outbound Calls. It is recommended for customers with Tasks in this state to Cancel them to free the capacity of the Flex Agents assigned to them to have the ability to accept Inbound Calls. Customers can also update their Workers with a new Activity while also providing RejectPendingReservations=true to reset their Flex Agent state via API.
From Twilio’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Twilio, started 2020-11-25 03:37 UTC, resolved after 0 min, 1 update(s).
- Title
- Flex Dialpad Degradation Caused Stuck Tasks
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/v238rmd2fjyq
Twilio profileRecent Twilio incidentsAll outages on November 25, 2020Twilio in November 2020MarkdownJSON