Overview
Contact form issues usually fall into one of two categories:
False positive - the form shows an error message, but the email was actually sent and received. This is a UI display issue, not a functional one.
Real failure - the form did not send the email, and the error is genuine.
This guide walks you through how to check which situation you're dealing with using your browser's network inspector, and what to do next in each case.
Step 1 - Open the Network Inspector
Before submitting your contact form, open your browser's developer tools to monitor network requests.
Open your website in a browser.
Right-click anywhere on the page and select Inspect (or press F12 on Windows / Cmd + Option + I on Mac).
Click the Network tab in the developer tools panel.
Make sure recording is active (the circle icon in the top-left of the Network tab should be red).
Step 2 - Submit the Contact Form
With the Network tab open:
Fill in your contact form fields as normal.
Click the Submit (or Send) button.
Watch the Network tab - a new request will appear when the form submits.
Step 3 - Find the Form Submission Request
In the Network tab, look for the request that was triggered by your form submission. It will usually:
Appear immediately after you clicked Submit.
Have a name like lead , and will have lead_v3 or a similar endpoint path.
Be listed as a POST request (you can filter by Fetch/XHR to narrow it down).
Click on that request to inspect it.
Screenshot of the successful form request down below:
Step 4 - Check the Status Code
With the request selected, look at the Status column on the Headers tab and Response tab to check the response of the request.
✅ Status 200 - Form submitted successfully.
A 200 status code means the server accepted the form submission without errors.
If you also received the email → everything is working correctly. The error message shown on the form is a false positive - a UI display bug, not a functional issue. The form is working as intended; only the confirmation message in the interface is incorrect.
If you did NOT receive the email despite a 200 status and response {“success”:true} → the server accepted the request but something went wrong downstream (e.g. email delivery, spam filters). Check your spam/junk folder first, then see Step 5.
❌ Response {"success":false} - Real failure
Such response means the submission genuinely failed:
Bad request (form data missing or malformed).
Server error (something went wrong on the backend).
In this case the error shown on the form is accurate, not a false positive. Proceed to Step 5. Example of failed contact form request response:
Step 5 - What To Do Next
If it's a false positive (200 status + email received)
The form is functional - only the UI confirmation message needs fixing. You can ask Commet to correct the error display:
Open a chat with Commet in your Sintra workspace.
Describe the issue, for example:
"My contact form is working (emails are being received and network requests return 200), but the form is showing an error message after submission. Please fix the UI so it shows a success message instead."
Attach a screenshot of the error message if helpful (see below for screenshot tips).
Commet will locate the relevant code and update the confirmation logic.
Once fixed, publish your website to make the change live.
If it's a real failure (response of the contact form contains {"success":false})
The form is not sending emails. Share the details with Commet so it can investigate and fix the underlying issue:
Take a screenshot of the Network tab showing the failed request and its status code.
Click on the request and copy the Response body (this often contains a more specific error message).
Open a chat with Commet and share - the status code you saw, the response body or error message and a screenshot of the Network tab if possible.
Ask Commet to diagnose and fix the issue, for example:
"My contact form is returning a 500 error on submission/response is success:false and emails are not being received. Here is the response and the request: [paste response and network request itself]. Please investigate and fix it."
Publish the website once Commet confirms the issue is resolved.
Afterwards test the form again using the same network inspection steps above.
What information to gather for the easiest resolution?
When sharing evidence with Commet, the most useful information is:
The Network tab showing the request name, method (POST), and status code.
The Response tab (within the selected request) showing any error message returned by the server.
The form itself shows the error message displayed to the user.
You can add screenshots directly into the Commet chat by dragging and dropping or using the attachment icon.
Still Having Issues?
If you've followed these steps and are still unsure what's happening, open a chat in your Sintra workspace and share:
The status code from the Network tab.
Whether or not you received the email.
A screenshot of the error shown on the form.
Our team can help you determine whether it's a UI fix or a deeper configuration issue.