Why Am I getting unexpected results. What should we check for?

If you're getting unexpected results from RChilli’s Search & Match API, several factors could be contributing. Here's a detailed diagnostic checklist and resolution guide to help you identify and correct the issue.

Common Reasons for Unexpected Results

1. Data Was Not Parsed or Indexed Properly

• Symptom: Search returns missing fields or irrelevant records.

• Check:

  • Was the data parsed before indexing?

  • Was the document indexed using ParseAndIndex or IndexDocument?

• Fix:

  • Re-parse the document using the Resume or JD Parser.

  • Re-index using the correct schema.

Parse and Index API

2. Wrong or Missing subuserid in API Calls

• Symptom: Indexed records aren’t appearing in searches.

• Check: Are you using the correct subuserid for both indexing and search requests?

• Fix:

  • Ensure consistency between the subuserid used for indexing and searching.

  • Confirm that you're calling the API in the production environment, not demo.

3. Default Search Configuration May Not Match Your Use Case

• Symptom: Irrelevant matches or poorly ranked results.

• Check: Are your query weights (skills, job title, location, etc.) aligned with what matters most to your business?

• Fix:

  • Use custom scoring weights via the front-end or request support to configure backend weights.

  • Enable the Query Analyzer for advanced keyword tagging and intelligent matching.

Scoring Configuration Help

4. Taxonomy and Ontology Not Used or Outdated

• Symptom: Missed matches due to synonyms not being recognized (e.g., “DevOps” ≠ “Development Operations”).

• Check: Are you enriching data with RChilli’s Taxonomy 3.0?

• Fix:

  • Enable reqtaxonomy: true in parsing API settings.

  • Consider a Taxonomy API call to normalize and expand keyword sets.

Taxonomy API Overview

5. Duplicate Documents in Index

• Symptom: Same profile showing up multiple times or conflicting versions.

• Check: Have you implemented de-duplication at the time of parsing or indexing?

• Fix:

  • Enable duplicate checks in your parsing settings or maintain documentId per record to update instead of re-adding.

6. Incorrect or Incomplete Field Mapping

• Symptom: Fields like experience, education, or skills not showing correctly in results.

• Check:

  • Are you using correct field names in your JSON?

  • Are dynamic settings like reqeducationdrill, reqskillsdrill enabled?

• Fix:

  • Enable required dynamic fields during parsing.

  • Verify that indexing schema matches RChilli’s expected structure.

Dynamic API Settings Guide

7. Query Misconfiguration or Syntax Errors

• Symptom: No results or irrelevant ones despite data being present.

• Check:

  • Are you using correct search syntax (e.g., Boolean operators, field filters)?

• Fix:

  • Use the Query Analyzer to test queries.

  • Use API docs for guidance on SimpleSearch, Match, and AdvancedSearch.

Troubleshooting Checklist

Need Hands-On Help?

• You can test your query in MyAccount using your API key.

• Contact support@rchilli.com with:

  • Your API request

  • Sample indexed document

  • Example of unexpected result