> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apostra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Diagnose Stuck Media Buys

> Use API evidence and the customer troubleshooting workflow to understand a media buy that is not progressing.

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
Apostra. It explains each lifecycle checkpoint, the evidence to collect,
and when support needs to become involved.

<Card title="Open the troubleshooting guide" icon="book" href="/v2/guides/diagnosing-stuck-media-buys">
  Follow the canonical media-buy diagnosis procedure.
</Card>

## Apostra support trace

Apostra support operators can open the internal stitched trace for any media-buy
identifier:

```http theme={null}
GET /api/v2/admin/media-buys/{mediaBuyId}/trace?buyerCustomerId={buyerCustomerId}
```

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`.