Why is an empty resume indexed successfully in the job application workflow?

 An empty, corrupted, or unreadable resume should not be indexed as a valid candidate document. When RChilli Resume Parser does not find usable resume content, it returns:

Error Code: 1014
Error Message: Corrupted data/No Content Found

However, in a job application workflow, the connected application or integration may create the candidate or job application record before validating the RChilli parser response. As a result, the document may appear to be successfully indexed even though the parser returned an error.

To troubleshoot the issue, verify that the job application workflow:

1. Validates the complete RChilli API response before indexing the document.
2. Stops processing when error code 1014 is returned.
3. Does not create or update the searchable resume record when parsing fails.
4. Records the API request, response, and indexing status in the integration logs.
5. Sends the correct service URL, required request parameters, and valid Base64 file data.

If the issue persists, contact at RChilli Support and provide:

• Resume file
• Job application ID
• RChilli API request and response
• Error code and message
• Relevant workflow or integration logs
• Date and approximate time of the issue

Relevant Help Documents:

• How to Fix Error 1014 While Calling the API
• Resume Parser Error Codes