OFFLINE
Awaiting data
Twilio service status
MinormonitoringCloud

Flex UI Realtime Statistics Showing Inaccurate Longest Waiting Task Data

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. (Affected: Flex Insights)

Started

Sep 22, 2026, 8:44 PM UTC

Status

Ongoing

Elapsed

2h 33m

Flex Insights
InvestigatingSep 22, 8:44 PM

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.

MonitoringSep 22, 9:39 PM

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.

InvestigatingSep 22, 9:39 PM

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.

IdentifiedSep 22, 10:06 PM

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.

MonitoringSep 22, 10:39 PM

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.