- Finding out what went wrong
The async write loop
Request size
Status enum
Rejected rows
Polling cadence
Idempotency
Errors
Public Jobs Get
Finding out what went wro...
| What you see | Where the reason is |
|---|---|
413 PAYLOAD_TOO_LARGE on the POST itself | The body is over 200 MiB (see Request size). Nothing was read or queued; send the rows in several smaller requests. |
400 VALIDATION_FAILED on the POST itself | The response body: error.details[] lists every offending field (loc, msg, type). Nothing was queued. Log that body on your side — for a large batch it can run to many kilobytes. |
Job FAILED | error_message on GET /jobs/{job_id}, and errors[] when rows were rejected. Nothing was written. |
Job COMPLETED with error_count > 0 | errors[] — one entry per rejected row (the first 1,000) with row_number and identifier; every other row was applied. |
Admins can also look up every write request and every job with its outcome under Settings → Integrations → Logs in the Mercura app; the requests sent with one API key alone are under Settings → Integrations → For developers → API → Logs.