FAQ – RChilli HelpDesk

We’re adopting the new Redaction API to minimize credit usage. Is it necessary to disable any old workflows or templates?
Is it possible to fully automate the one-to-many Search & Match functionality?
How can semantic matching for degrees be enhanced in Search & Match?
How should non-resume documents be categorized to prevent parsing errors?
What happens to the earlier resume in the Oracle when a new file is uploaded?
Where is the RChilli PeopleSoft configuration file located in MyAccount?
Does the Search and Match API require a Sub User ID?
How does Sub User ID interact with the Redaction feature to ensure bias-free hiring?
Can templates be customized individually for each Sub User ID?
Does including a Sub User ID modify the API response or disrupt production?
How can it be confirmed that a Sub User ID is working correctly?
Which RChilli APIs support the Sub User ID?
How does RChilli support job and skill intelligence tuning?
What is the process for switching from the Salesforce marketplace app to RChilli APIs?
What is the appropriate approach when parsing performs correctly for English but fails for Arabic other languages?
What are “PLG” or plugin charges in usage, and how are they related to the Redact plugin?
How can I monitor RChilli API credit consumption and efficiently investigate sudden usage spikes?
All job posts on the career site are showing 'India' by default. How can we fix the location mapping?
A bulk run was initiated for 50 profiles(Resume), but only 49 were processed. Please advise what needs to be verified.
Purchased Customized Taxonomy, Bulk Profile Upload, Browser Plugin, and Email Importer. What should be set up first on our side?
When testing Search & Match, which index type should be used (Resume or JD), and what’s the correct order for testing?
For the Salesforce AppExchange app, is RChilli able to change or cancel the subscription plan?
How do credits get consumed during the formatting, indexing, or search processes?
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?