incident-analysis

To find the root cause of failed transfers and missing events, trace the end-to-end event chain from transaction creation to completion to locate the first failing link. You can verify event delivery by checking transaction logs and reconciling the ledger state.

Trace delayed event delivery by applying system-level reasoning to hypothesize potential failure modes and verify them against event tracing data. This process locates exactly where notification failures or transaction delays occur within the event-driven backend.

Balance misupdates often occur due to delayed event delivery or reversible transactions disrupting data consistency. Check data consistency by comparing Ledger sums to aggregated Balance to identify anomalies and verify the correct ledger state.

Debugging production incidents requires access to transaction logs, event tracing data, and ledger state. These inputs are necessary to verify event delivery, reconcile state, and guide corrective actions for transaction delays.

Yes, this incident analysis applies to both production and development incidents involving balance misupdates, transaction delays, or notification failures. It traces the event chain across the event-driven backend to pinpoint failures in any environment.