George Lambert
f3dc0e6eee
Some checks are pending
offline / test (push) Waiting to run
In-process trace console validates hops, faults, recoveries, and suggested changes before zapier-platform push. User guide covers signup through central-chain and bulk-summary tree-node hash lookup.
14 lines
1 KiB
Markdown
14 lines
1 KiB
Markdown
# 11. Errors, billing, retries
|
||
|
||
| HTTP | Zapier mapping | What you should do |
|
||
|------|----------------|--------------------|
|
||
| 400 | validation | SHA-256 must be 64 hex chars; supply Data or SHA256. |
|
||
| 401 | auth | Re-paste API key; it may have been regenerated. |
|
||
| 402 | QuotaExceeded | Reload prepaid credit in the portal (`upgradeUrl` in the error). |
|
||
| 403 | PlanUpgradeRequired | Batch / wait / tree lookup may be paid-only. |
|
||
| 404 | empty search | Not itemized — try tree-node search before creating a new seal. |
|
||
| 504 / pending | timeout | Use the Completed trigger; do not loop wait in the same step. |
|
||
|
||
Middleware retries `jobs.watch` / `jobs.events` once when NATS drops (simulator: enable **recover**). Zapier itself retries failed HTTP according to your Zap settings — keep creates **idempotent** (re-registering the same hash returns the original seal).
|
||
|
||
Delays: if the simulator flags hops over 200ms, do not raise Zapier’s step timeout until chain poll interval and archive query window (`WAIT_ARCHIVE_MS`) are measured on NS1.
|