FAQ – RChilli HelpDesk

What steps should be taken if intermittent errors, such as a 400, occur during bulk uploads?
How can the integrity of a PeopleSoft node be validated after uploading the configuration files?
What’s the best approach for keeping data up to date—annual enrichment or one-time reprocessing—and what information does RChilli update?
How can it be verified whether the LLM/GPT parser was active, or if the process fell back to the standard parser?
What does "Job Profile" mean, and how does it impact search and redaction?
How can job-to-job or resume-to-job matching be refined, and where can scoring settings be adjusted?
What’s the easiest approach for bulk parsing: email drops, zip files, or FTP? When should each method be applied?
How can bias-free screening be achieved? Is it possible to remove PII (Personal Identifiable Information) or implement job-zone-based redaction?
What is the most effective way to standardize resumes into one template for the brand, and which credits should be used?
Which method offers the quickest deployment of RChilli: RScript or the full API? What should determine the best option?
Is there a way to validate or audit the accuracy of resume parsing results through RChilli?
Can RChilli’s JD Parser be used to extract and analyze data from job descriptions scraped from competitor job boards?
Does RChilli support bulk execution of Search & Match, such as matching a large dataset (e.g., 10,000 resumes) against a single JD?
Does RChilli Search & Match support real-time candidate matching during live job application submissions?
How can we customize scoring rules based on specific recruiters or departments?
How can I find the Secret Key in MyAccount for Staging and Production environments?
Which resume format—PDF, DOCX, or TXT—provides the best parsing accuracy and performance when processed through RChilli?
The qualification field in the OneMatch response is not matching correctly. What steps should I take to resolve this?
The score in my OneMatch output is significantly lower than before. What could be causing this drop?
What are RChilli’s current compliance and security certifications?
Can RChilli handle bulk parsing of previously stored candidate resumes from our ATS?
Can RChilli automatically click a CTA link within an email to download and parse a resume?
Does RChilli return parsed data in JSON format when using email parsing?
Can RChilli parse resume data directly from the email body even if there is no attachment?
Can RChilli parse resumes directly from LinkedIn via API?
What is the process for a Oracle Booster client to obtain an OB Client ID?
Is it possible to switch between staging and production API keys dynamically during integration testing?
What steps should be taken if resume parsing fails on the career site but works correctly on RChilli's end?
The resume import in Oracle failed to parse correctly, despite working earlier. What could have changed?
What could be causing the resume parser to return a 200 response without displaying any data on the Oracle career site?