Studio Flows With Timer Widgets Impacted

Incident Report for Twilio

Resolved

Studio Flows incident has been resolved and service is operating normally at this time.

Posted Jan 12, 2024 - 10:53 PST

Monitoring

The problem causing a fraction of Studio executions with timers created before 01:18 PT and expiration after 01:18 PT on 01-12-2024 has been fixed. We will continue to monitor for system stability and will provide an update in 30 minutes or sooner if more information is available.

Posted Jan 12, 2024 - 10:06 PST

Update

Studio is back to normal. Any new executions relying on timers are working fine. Our engineers have identified the issue causing fraction of Studio executions that used widgets which rely on timers created before 01:18 PT with expiration time after 01:18 PT on 01-12-2024, which would result in that execution becoming stuck, and are working to deploy a fix. We expect to provide another update in 4 hours or as soon as more information becomes available.

Posted Jan 12, 2024 - 08:09 PST

Identified

Studio is back to normal. Any new executions relying on timers are working fine. Our engineers have identified the issue causing fraction of Studio executions that used widgets which rely on timers created before 01:18 PT with expiration time after 01:18 PT on 01-12-2024, which would result in that execution becoming stuck, and are working to deploy a fix. We expect to provide another update in 2 hours or as soon as more information becomes available.

Posted Jan 12, 2024 - 06:14 PST

Update

We have observed an issue with Studio workflow timers that were active at 01:18 Pacific Time. Executions that used widgets which rely on timers may have been impacted, which would result in that execution becoming stuck. Our engineers are investigating this further. We will provide another update in 1 hour or soon as we have more information.

Posted Jan 12, 2024 - 05:25 PST

Investigating

Our monitoring systems have detected a potential issue with Studio workflow timers expiration. Our engineering team has been alerted and is actively investigating. We will update as soon as we have more information.

Posted Jan 12, 2024 - 04:50 PST

This incident affected: SERVERLESS (Studio).