Skip to main content
Open Conversions. The status column names the failure, and hovering the badge reads HTTP <code> · attempt <n>.

What each status means

No row exists at all

failed: non-retryable errors

retrying and dropped: retryable errors

The retry queue drains every 5 minutes, and after three failed attempts the row turns dropped. Five consecutive 5xx responses from one platform open a 60-second circuit for that workspace. We also cap our own send rate per platform.

skipped reasons

A rule_circuit_open row is written with status failed, not skipped, which keeps it in your failure count.
Meta and TikTok have no validate-only mode, so a test without a Test Events code would create a real billable production conversion. We refuse that test instead.

sent but the platform reports nothing

sent means the platform returned success. It doesn’t mean the platform credits the conversion.
Do not enable two rules for the same event and destination. Each rule delivers separately, and the platform counts the conversion twice.

Verify a fix

  1. Send one new source event.
  2. Filter Conversions on that platform.
  3. Confirm a new row reads sent.
  4. Open the platform’s Test Events surface and find the event.