Troubleshooting
Start from the recorded stage: receipt, verification, storage, delivery or replay.
The event is missing
- Confirm the selected organization and copied source ingress URL.
- Check whether the source was paused; dropped acknowledgements are not stored events.
- Check the actual sender response and quota/body-size errors. A 202 without checking dropped/event_id is not enough.
- Refresh persisted history after a Live pause or connection gap. A quiet stream does not prove the event was lost.
The signature is not valid
Read the event’s recorded reason. Verify that validation was enabled, the provider is supported and the configured secret matches the chosen scheme. Adyen’s implemented raw-body header scheme is not its notificationItems canonical-field scheme.
Do not assume a newly changed secret repairs history. Invalid original events remain ineligible for replay; send a new controlled event to validate updated configuration. Not checked is different from invalid.
The body is unavailable or unformatted
Content is retained only for accepted async captures within 30 days of receipt. Old purged events cannot be recovered. Empty content is explicitly available with zero bytes.
A failed load offers Retry and does not mean empty. Unsupported encoding/binary appears as base64; malformed, complex or unsupported text falls back to original. Formatting and preview limits never modify the stored bytes.
Capture succeeded but delivery did not
Read the original delivery state and reason. No destination, required unverified signature, source changes or paused configuration can cancel delivery without attempts. A capture marked Received says nothing about remote HTTP success.
A corrected current source with retained eligible content may allow an explicit replay. The source destination must satisfy the sender’s HTTPS/network policy; the dialog cannot override it. A timeout may follow a remote effect, so reconcile with the receiver before creating a separate replay.
Replay conflict or uncertainty
After a definitive 409, refresh the source/eligibility and review current settings before a new confirmation. For an uncertain network/5xx result, retry the same request identity and original inputs; do not manufacture a new action.
Repeated accepted keys can return a terminal action. Check the history rather than assuming a fresh queued job or permanent success.
Account, reports or alerts
Expired sessions may need Google sign-in again. Wrong organization/role can explain 403/404 without a service outage.
Usage reports label their time windows and are not invoices. Alert email and invitation email transports are not connected; a stored rule/invitation does not prove email delivery. Slack Test is an external action when configured.