Skip to content

Incident detail

Flex UI Realtime Statistics Showing Inaccurate Longest Waiting Task Data

Resolved incidentMinor

Timeline window

to

Get alerted the next time Twilio breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    We are investigating an issue where a subset of Flex customers may see inaccurate real-time statistics data in the Flex UI. Specifically, the “longest waiting task” metric may display inflated values. Our engineers are working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  2. Monitoring

    We are still investigating an issue where a subset of Flex customers may see inaccurate real-time statistics data in the Flex UI. Specifically, the “longest waiting task” metric may display inflated values. Our engineers are working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  3. Investigating

    We are still investigating an issue where a subset of Flex customers may see inaccurate real-time statistics data in the Flex UI. Specifically, the “longest waiting task” metric may display inflated values. Our engineers are working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  4. Identified

    We are aware of inaccurate data being returned from Flex Queue Stats page, particularly for longest waiting task metrics. Our team has identified the cause and is actively working to fix the data discrepancy. If you are continuing to experience this issue, please contact support with your account SID and queue ID to expedite resolution. We will provide another update in 1 hour or as soon as more information becomes available.

  5. Monitoring

    Our team has identified the cause and has fixed the data discrepancy.  If you are continuing to experience this issue, please contact support with your account SID and queue ID to expedite resolution. We will provide another update in 2 hours or as soon as more information becomes available.

  6. Resolved

    Our engineers have monitored the fix and confirmed the issue with Flex UI Realtime Statistics Showing Inaccurate Longest Waiting Task Data has been resolved. All services are now operating normally at this time.

Keep exploring

More from Twilio

Neighboring incidents on Twilio's timeline and the rest of their record on OutageDeck.