Troubleshooting
Locate the first broken boundary between the page, intake, storage, and destination.
Start with the symptom
- No request: inspect native validation, submit handlers, and the browser console.
- 404: verify the form key, endpoint, and active state.
- 422: compare names and values with the published schema.
- 429: inspect rate and plan capacity.
- 202 but no message: search the workspace using the request or receipt ID.
- Stored but no destination: inspect recipient, connection, and provider history.
| Symptom | What to check |
|---|---|
| Form not found | Key, publication, active state, and action URL |
| Empty or incorrect data | name attributes and published schema |
| Error 422 | Invalid fields, CAPTCHA, and configuration |
| Error 429 | Quota, rate limit, and Retry-After |
| Error 413 or 415 | Body size and content type; separate file journey |
| Message stored, email missing | Verified recipient, notification mode, and delivery history |
| CORS / origin error | Protocol, subdomain, port, and allowed origins |
Read notification state
Queued, provider accepted, delivered, bounced, complained, failed, and unknown outcomes require different actions. Do not resend automatically when a destination may already have received the item.
Prepare a useful support request
Include the public form ID, timestamp, request ID, deployed page, response status, and expected boundary. Remove credentials and visitor content that is not needed for diagnosis.
Documentation reviewed on October 20, 2026Suggest an improvement →