How do I troubleshoot "Resume Parsing succeeded but containers not found" errors?

The error “Resume Parsing succeeded but containers not found” typically indicates that although the resume was successfully parsed, the system is unable to locate or match the parsed data to the predefined containers (fields) where it should be stored. This can happen due to configuration issues, missing mappings, or a parsing output mismatch.

Here’s a detailed guide on how to troubleshoot and resolve this issue:

Possible Causes & Solutions

1. Incorrect Configuration of Parsing Containers

RChilli’s parsing output is mapped into containers or fields within your system, such as “Contact Information,” “Skills,” “Experience,” etc. If these containers are not set up correctly or do not exist in your system, the parsed data cannot be properly placed.

Solution:

• Check if the container fields in your system are correctly set up to receive the parsed data.
• Ensure that the field names in your system match exactly with the field names in RChilli’s parsing output (case-sensitive).
• If you're using a custom integration, review the mapping between the parsed fields and the containers in your database or platform.
• For Resume Parser API, make sure that the FieldList (in the API request) is correctly configured to receive the parsed data.

Check how to customize data mapping.

2. Missing or Misconfigured API Settings

RChilli allows for flexible API settings, including toggling specific sections like OCR, skills, and field configurations. If these settings are misconfigured, the data might not populate the correct containers.

Solution:

• Review your API settings and ensure that the necessary fields are enabled and mapped correctly. Specifically, check the fields for:
  • Skills
  • Experience
  • Education
  • Contact Information
• Ensure that any custom configurations (like excluding certain fields or limiting the output) are not preventing the data from being properly mapped to the containers.

Dynamic API Settings for Resume Parsing.

3. Unsuccessful OCR Parsing (If Applicable)

In some cases, if OCR (Optical Character Recognition) is required for parsing scanned or non-text resumes (like images or PDFs), it might fail, and the resume is parsed without the necessary data in the containers.

Solution:

• If you’re working with scanned documents or images, ensure that OCR parsing is enabled.
• If OCR is failing, check for any issues with the OCR setup or whether the resume format is supported by RChilli’s OCR.
• You can also check for OCR parsing issues in the API response logs. If OCR fails, it can prevent the data from being extracted and placed into the correct containers.

OCR Parsing Configuration.

4. Corrupted or Incompatible Resume Format

If the uploaded resume file is in an unsupported or incompatible format, it may be parsed successfully but without the necessary structured data. This can result in no valid container data being found.

Solution:

• Verify that the resume is in a supported format, such as PDF, DOCX, or TXT. If it's in an uncommon format, such as a scanned image, you may need OCR enabled.
• If parsing issues persist, try uploading a different resume in a known supported format (e.g., DOCX or PDF) to confirm if the issue is with the specific file.

   Supported Resume Formats for Parsing.

5. Parsing Configuration & Taxonomy Library Issues

If you are using Taxonomy (skills, job profiles, etc.) in the parsing configuration, errors in the taxonomy settings might result in data not being populated correctly into the containers.

Solution:

• Check that the taxonomy configuration is set up correctly for the data being parsed (skills, job titles, etc.).
• Ensure that the Taxonomy API is being called properly if you rely on it for skill matching or enriching the parsed data.

Learn about Taxonomy Configuration.

Suggested Workaround

While you're troubleshooting the issue, consider using the Dynamic API Settings to modify the parsing configuration on the fly. This allows you to control which data is returned and how it is parsed, helping you pinpoint which section or field might be causing the issue.

Dynamic API Setting Guide.

Still Not Resolved?

If you are unable to resolve the error with these steps, consider contacting RChilli Support to assist with advanced debugging: support@rchilli.com