Diagnose and fix problems with event registration forms connected to Cotonity agents, including validation errors, CORS issues, webhook misconfigurations, and browser compatibility problems.
Browser-side errors and validation failures
When a registration form fails to submit, start by checking the browser console for JavaScript errors. Open the browser developer tools (F12 in most browsers), navigate to the Console tab, and attempt the submission. Red error messages point to client-side issues such as a missing required field that is hidden from the user, a JavaScript validation script crashing on an unexpected input value, or a Content Security Policy header blocking a necessary script. If the console shows no errors but the form still does not submit, check the Network tab to see whether an HTTP request was actually sent and what response it received.
CORS and cross-origin request errors
If the registration form is hosted on a different domain than the Cotonity webhook endpoint it submits to, the browser will block the request unless the endpoint returns the correct CORS headers. In the browser Network tab, look for a request with a status of '(failed)' accompanied by a CORS error in the console. To fix this, navigate to the webhook trigger's settings in Cotonity and add your form's hosting domain to the 'Allowed origins' list. Cotonity will then include the appropriate Access-Control-Allow-Origin header in its responses. If the form uses a custom submission endpoint on your own server that then forwards to Cotonity, the CORS fix should be applied to your server rather than to the Cotonity webhook.
Webhook endpoint and payload validation
The Cotonity webhook trigger endpoint validates incoming payloads against the schema defined in the trigger configuration. If the form submits a field name or value that does not match the expected schema — for example, submitting `first_name` when the trigger expects `firstName` — the webhook will return a 422 Unprocessable Entity error and the form's success handler will not fire. Compare the form's field names exactly against the fields defined in the trigger schema. Field names are case-sensitive. If you recently updated the trigger schema, regenerate the webhook endpoint URL from the trigger settings, as the old URL may still point to a cached schema version.
Testing the submission pipeline end-to-end
Use Cotonity's built-in webhook test tool to isolate where the failure occurs. In the trigger settings, click 'Send test payload' and observe whether the test run completes successfully. If it does, the issue is in the form itself or the connection between the form and the webhook. If it fails, the problem is in the Cotonity workflow configuration. For additional debugging, temporarily add a Log step as the first step in the workflow to capture the raw incoming payload — this lets you see exactly what data the form is submitting versus what you expect. Remove the Log step once the issue is resolved to avoid storing unnecessary run data.