Troubleshooting · Developer docs

Troubleshooting

Grouped by symptom, never by module, because the person with the problem does not know which module has it. One hundred questions across ten pages, each answered with the causes in the order they usually turn out to be true.

Answer API requests

My form submission through the API answered 207

A 207 is stored but not complete. Some answers failed the form's rules; they are kept, marked invalid, and the message reads "The Form Submission has been saved successfully, but it contains validation errors." Nothing that counts or acts on completed submissions sees it, so a client that treats every 2xx as success thanks the visitor for a submission nobody will read.

Show the errors from validationErrors, keyed by element name, and keep the submission's token from the answer. When the visitor corrects them, send every answer again to PUT /cdna-api/forms/submission/{token}, which completes the same submission: a new POST would start a second one. Treat 200 as done and 202 as "go and pay".

Every status is in Submitting a form through the API; a working server route is in Submit a Core dna form from a React or Vue front end.

In the API reference: Submit a form.

More in API requests

  1. One visitor's form shows up twice among the submissions
  2. Showing an error when a JS-model submission is rejected
  3. A conditional field never appears, or never hides
  4. My properties fields come back as "Error: Getter for property … not found", or glued together
  5. "414 Request-URI Too Long", or my long properties selector stops working

Was this page helpful?

Your answer goes to the docs team.