Critical: Stream Closed Due to Server-Side Timeout in flagd Runtime Flow
CRITICALError
Error Frequency
Off
Error Details
First seen:1 month ago
Last seen:26 secs ago
Stack:go
Service:flagd
Stack Tracestream closed due to server-side timeout
Error message
stream closed due to server-side timeout
No stack trace captured — common for browser console errors. Check the User Journey for the events that led up to it.
Activity
User journey33 events before error
May 27, 12:42:49flagd.evaluation.v1.Service/EventStream
_MultiThreadedRendezvous: <_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.DEADLINE_EXCEEDED
details = "Deadline Exceeded"
debug_error_string = "UNKNOWN:Error received from peer {grpc_status:4, grpc_message:"Deadline Exceeded"}"
>
+0smessage
+0smessage
+20smessage
+40smessage
+1m 0smessage
+1m 20smessage
+1m 40smessage
+2m 0smessage
+2m 20smessage
+2m 40smessage
+3m 0smessage
+3m 20smessage
+3m 40smessage
+4m 0smessage
+4m 20smessage
+4m 40smessage
+5m 0smessage
+5m 20smessage
+5m 40smessage
+6m 0smessage
+6m 20smessage
+6m 40smessage
+7m 0smessage
+7m 20smessage
+7m 40smessage
+8m 0smessage
+8m 20smessage
+8m 40smessage
+9m 0smessage
+9m 20smessage
+9m 40smessage
+10m 0sexception
Issue events
AI Assistant