Troubleshooting

Cloudflare connection or deployment

If OAuth returns an error, reopen Runtimes and inspect the connection result. Confirm the account has the requested Workers and zone permissions. A successful OAuth return is not a successful deployment; wait for completion and run Verify. Correct the named binding/resource issue instead of creating parallel resources manually.

API errors

• 401: missing, revoked or wrong-Runtime key.
• 403: insufficient permission, feature gate, sandbox restriction or policy block.
• 409 invalid_idempotent_request: key reused with a different payload.
• 413: request, workflow or attachment exceeds a limit.
• 422: domain, topic, suppression, deliverability or provider precondition failed.
• 429: rate limit or daily quota; back off with the same idempotency key.
• 5xx: transient Runtime/provider fault; inspect Logs before retrying.

Delivery and automation

Verify SPF, DKIM, bounce MX and DMARC. Distinguish accepted, queued, provider-rejected, bounced and complained states. Check Workers Paid, suppressions and preferences. For automation, matched: 0 means no active workflow has the exact event; accepted: 0 with matches usually means duplicate eventKey; waiting is a Delay; failed exposes the step error.

Submit a ticket with Runtime/version, message or run ID, timestamp, HTTP status and error code.