Delivery debugging and retry flows

Outbound delivery inspection belongs to operator workflows in the portal. Support can inspect statuses, attempts, HTTP results, and the customer runtime context tied to a delivery without changing backend integration code.

Delivery retries belong to the portal-side operational surface, alongside customer investigation and manual recovery. Keep retry handling separate from the runtime API your product calls during checkout, access, and usage flows.

When a delivery problem appears, inspect the subject, entitlement state, checkout attempts, and outbound delivery history together before retrying.

The receiver-side contract still lives in outbound webhook delivery contract. This page focuses on the portal workflow for inspecting and requeueing deliveries after you understand the underlying runtime state.

• Customer says access is missing: inspect the customer by subject_ref, confirm the current access decision, review current entitlements, then inspect checkout attempts and outbound delivery history together.
• Outbound webhook delivery failed: review delivery status, attempts, last HTTP status, last error, and next retry timing before deciding whether to requeue from the portal.
• Refund unexpectedly revoked access: inspect entitlement history, refund/dispute timing, and the resulting runtime status before applying manual recovery.
• Credits depleted unexpectedly: inspect usage history, current usage_remaining, and whether any manual adjustments were applied.
• Manual grant recovery flow: inspect runtime state first, grant or adjust through the portal only after review, then verify the resulting access decision and outbound delivery history.