Skip to main content
Begin with the media buy’s current phase, latest failure, approval state, and source or seller evidence. Preserve structured error codes and recovery fields; do not infer a successful transition from an HTTP or MCP transport success. The troubleshooting procedure is shared with people operating the same buy in Interchange. It explains each lifecycle checkpoint, the evidence to collect, and when support needs to become involved.

Open the troubleshooting guide

Follow the canonical media-buy diagnosis procedure.

​
Scope3 support trace

Scope3 support operators can open the internal stitched trace for any media-buy identifier:
Include buyerCustomerId whenever a storefront media-buy identifier is buyer-scoped or could be reused by more than one buyer. Without that scope, an ambiguous identifier returns a conflict instead of guessing which transaction to expose. Keep the same parameter when fetching one event with eventId.