When a candidate can’t complete their application, they usually see a “Failed to submit” message or the form freezes after they click apply. This is almost always caused by a problem passing candidate data to your ATS.
Application errors need to be raised quickly. Every hour the error persists, candidates lose the ability to apply. Treat submission errors as Priority 1 unless they affect only a small number of roles.
Reproduce the error yourself
Open the job link the candidate was applying to and attempt to complete an application. Note exactly where the process breaks — which step and what message appears.
Check if it affects one job or all jobs
If only one or two jobs are affected, the issue is likely with how that specific job is configured in your ATS. If all applications are failing, there may be a wider integration issue.
Gather the job URL and any error messages
Copy the full URL of the job page. If the candidate shared a screenshot of the error, keep that too. This information speeds up diagnosis significantly.
Raise a ticket with inploi support
The job URL
A description of where the application fails
Any error text or screenshots
The approximate time the error started
Some submission errors occur because a question type in your ATS application form is not yet supported by inploi. If a new question type has recently been added to your ATS, mention this when you raise the ticket.
What to do if this doesn’t work
If inploi support cannot replicate the error, ask the affected candidate to try a different device or browser. Some errors are caused by browser extensions interfering with the form. If the error is intermittent, it may be linked to your ATS being temporarily unavailable.
Related articles
