Troubleshooting
Find the failed provider or platform stage and recover without duplicating a payment or rewriting evidence.
On this page
Start with context
- Confirm merchant, integration, environment, and deployed Carden key.
- Save HTTP status, request ID, preparation ID, attempt ID, event ID, and safe issue paths.
- Identify import, preparation, provider execution, report delivery, or settlement reconciliation.
- Inspect the source of truth for that stage before retrying.
Common failures
| Symptom | Action |
|---|---|
| Invoice missing | Check QuickBooks company, import coverage, checkpoint, and exact source record. |
| 401 | Replace missing, malformed, expired, or revoked Carden authentication. |
| 403 | Check provider, scopes, merchant, environment, and active integration state. |
| 400 | Correct strict JSON shape, required values, and content type. |
| 409 | Reconcile source revision, idempotency, event identity, provider aliases, or cumulative amounts. |
| 422 | Correct factual source or mapping data; keep unsupported records in review. |
| Report missing | Inspect the outbox, delivery response, duplicate acknowledgment, and environment. |
Recover report delivery
- Find oldest unacknowledged outbox events.
- Repair credentials or invalid fields before replaying permanent failures.
- Retry transient failures with the same body and eventId.
- Treat duplicate: true as acknowledgment.
- Reconcile unknown provider attempts before sending definitive later state.
A corrected observation gets a new event ID while the rejected event remains in audit history. Report failure never triggers another provider payment.