Documentation/Troubleshooting
Troubleshooting

Common errors

Start by opening Inbox and checking whether the message was saved. If it was saved but no email arrived, investigate notifications only. If there is no saved record, inspect the browser request, page origin and form status.

Nothing happens when I submit

Open the Network panel in browser developer tools and submit again. If no POST request goes to /f/your-form-id, check native required-field validation, the submit button and Console script errors. Confirm that the AI changes were published to the page you are visiting. Serve local files over HTTP instead of opening file:// URLs. After fixing the issue, submit and confirm the saved record in Inbox.

CORS or network error

The browser may hide the response for a disallowed origin. Compare the current page scheme, hostname and port with Sites → Settings → Allowed origins. Do not use mode: no-cors as a workaround: the page would be unable to read the save result. Correct the origin, then retry the same message from an allowed page.

Saving could not be confirmed

A lost network response does not prove that the server failed to save. Check Inbox first. To retry, keep the original content and _intent_id, obtaining a fresh Turnstile token if protection is enabled. Display success only after saved: true. Do not silently create a new intent and send the same message again.

409 conflict after editing a retry

One _intent_id identifies one message and cannot be reused with changed content. Restore the original content to retry or replay the result. For genuinely new content, let the visitor explicitly choose New message and create a new intent. Do not hide the conflict by automatically changing the intent.

Missing fields, attachments or oversized content

Every control you want to save needs a name. Use independent field names or explicit string serialization for checkbox groups and multi-select values; array and object values are unsupported. 413 too_large means the request is too big. 415 unsupported often means multipart, attachments or another unsupported encoding. Send JSON or URL-encoded string fields.

Origin does not match

When a submission is rejected for its origin, the form’s page shows a Recent origin mismatch notice with the exact rejected address. Compare it with Sites → your site → Settings → Allowed origins: scheme, hostname, and port must match exactly, and a preview subdomain is a different origin from the main domain. Correct the list, save, then submit a new test from the allowed page.

Form not found — a 404 on submit

The submission address does not match a live form. Copy the endpoint again from your form’s page: it looks like https://formpostbox.com/f/7f3c5b12-6db4-4f9a-91cb-7f5c5b7f8a31, and every form has its own id. Check that YOUR_FORM_ID was replaced, that you did not append a path, and that you re-copied the code after deleting and recreating a form.

The form is paused, or protection is not configured

Open the form and read the Configuration check panel. Status paused: select Enable form from the Forms list to accept submissions again. Turnstile Not configured: this is normal when the site is intentionally unprotected; if you want protection, save keys under Sites → Spam protection. Only with email notifications enabled, if the recipient is unverified or blocked: verify an address on the Recipients page, then select it in Form settings.

Message was not saved — keys or configuration

If you chose to protect the site, open Sites → your site → Settings → Spam protection: the Site Key shown there must match the one in your form’s code, and the Secret Key is write-only, so re-enter it from Cloudflare if you are unsure. Both keys must come from the same widget. Then open the form and check the Configuration check panel: Turnstile should read Configured when protection is enabled; Not configured is normal for an unprotected site. Also check that status is Active and, only if email notifications are enabled, that the recipient is verified and unblocked. Fix what is missing, save, and submit a new test.

Submission limit reached

The workspace has used its allowance for the current UTC calendar month. The sidebar shows used and remaining numbers, and a banner appears as the limit approaches. New submissions are rejected at the limit, so a rejected form should not show success. Free and paid monthly allowances reset at 00:00 UTC on the first day of the next month. Saved messages and their notification jobs are unaffected.

The Turnstile widget does not appear

Check that your Cloudflare widget’s Settings → Hostname Management includes the hostname of the page you are testing — hostname only, and remember that adding a hostname also covers its subdomains. Privacy tools and content blockers can hide the widget: try a private window with extensions disabled. If your site has a Content Security Policy, it must allow challenges.cloudflare.com; the browser console shows blocked requests. After fixing the hostname or the blocker, reload the page.

“Complete the Turnstile check, then try again.”

The form has no fresh token for this attempt. Finish the check and submit; a token is valid for 5 minutes and each one works only once. After a failure or expiry the examples clear the token and render a fresh challenge — do not reuse an old tab or a previous token. If the widget looks fine but saving still fails, confirm the Site Key and Secret Key come from the same widget.

Message saved: email not received

First check the notification timeline. If it says Email notifications off, saving worked and no email was requested. Enable notifications for future submissions if you need them; earlier inbox-only messages are not sent retroactively.

The message is safe in your inbox. Open it and read the notification timeline: Delayed — wait for the provider to retry. Failed — use Retry notification when the button is offered; retrying does not use more submission allowance. Bounced or Blocked — choose another verified, unblocked recipient in Form settings before retrying. Delivered — the provider handed the email to the recipient’s server; if it is not visible, check the spam or junk folder. Provider acceptance alone does not guarantee inbox placement.

See all HTTP status codes and recovery rules

Need help from your AI tool? Copy the troubleshooting prompt. Share redacted error codes, time and page origin; never share visitor messages, keys, cookies or full request bodies.

Still need help? Contact support@formpostbox.com. Include the guide topic and redacted error details, without keys or visitor messages.

Browse all topics ↑