commerce-events

Debug duplicate actions in commerce event workflows by inspecting the event history and querying idempotency keys to verify that retries are properly controlled. You can list, inspect, and acknowledge events to validate recovery across orders, payments, and inventory.

Inspect event payloads for specific commerce entities by querying the event log with a specific event ID or entity identifier. This allows you to quickly verify the audit trail, view metadata, and diagnose issues across outbox workflows.

Replay pending events in an outbox by reviewing the outbox state for synced or pending items and applying the replay action. You can then acknowledge the events to validate recovery and ensure end-to-end visibility for commerce operations.

Commerce payment events show inconsistent audit history when idempotency controls fail to prevent duplicate processing. Query the idempotency keys and outbox states to identify pending or synced events causing the discrepancy in the audit trail.

You can query idempotency keys to prevent duplicate order processing by reviewing the stored keys and their associated states. This helps identify and diagnose issues where retries may result in duplicate actions across commerce workflows.

Acknowledge events in commerce workflows after replaying them to validate recovery and ensure end-to-end visibility. This action confirms that pending outbox events have been properly processed and prevents further duplicate actions.