Delayed processing of Session Replay and Error data
Apr 6, 17:58 UTCApr 6, 19:02 UTC
Duration
1h 3m
Impact
Minor
Root cause
Database
LaunchDarkly, 90 days
9 incidents
Affected
Observability Data Ingest (Sessions, Errors)Observability (core functionality) - Observability Data Ingest (Sessions, Errors)
Final update
The delayed processing of Session Replay and Error event data has been resolved. All queued events have been processed and data ingestion is operating normally. No data was lost during this incident. Thank you for your patience.
Timeline
- Resolved · Apr 6, 19:02 UTC
The delayed processing of Session Replay and Error event data has been resolved. All queued events have been processed and data ingestion is operating normally. No data was lost during this incident. Thank you for your patience.
- Monitoring · Apr 6, 18:40 UTC
The delayed processing of Session Replay and Error event data has been resolved. All queued events have been processed and data ingestion is operating normally. No data was lost during this incident. Thank you for your patience.
- Identified · Apr 6, 18:15 UTC
We have identified the cause of the delayed Session Replay and Error event processing and a fix is in progress. The backlog is actively decreasing. No data has been lost , all queued events will be processed.
- Identified · Apr 6, 17:58 UTC
We are currently experiencing a delay in processing Session Replay and Error event data. Incoming data is being queued and will be processed , no data has been lost. Customers may observe a temporary lag in session and error data appearing in the LaunchDarkly UI. We have identified the root cause as elevated database utilization and are actively working to resolve the backlog. We will provide updates as processing returns to normal.
More from LaunchDarkly
Full historyEmail notifications are not being deliveredlasted 26mdelayed event processinglasted 0mElevated 5xx Errors (15:11–15:32 UTC)lasted 0mDelays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentationlasted 1h 37mElevated error rates in the LaunchDarkly applicationlasted 18h 55mFlag delivery errors in Streaming APIlasted 15m