There are five main causes for onboarding records failing to appear in SelectHR:
Invalid data in export
Cause: Data from Access Recruit doesn’t meet SelectHR field rules.
Common examples:
Text exceeding limits (e.g. job title > 100 characters)
Invalid characters (e.g. “£” in salary field, which must be numeric)
Key limitation:
Submitted applications cannot be edited
Workarounds:
Create the employee manually in SelectHR (New Employee workflow)
Reprocess in Access Recruit using Direct Candidate (remove problematic data)
Records sent to test system instead of live
Cause: After a database copy, test system is still configured to receive integrations.
Impact:
Records end up in test SelectHR
Cannot be transferred back to live
Fix:
Manually create employee in live SelectHR
Remove acloudrecruitment web server settings in the SelectHR test system Admin Tool to stop recurrence
Batch Job Not Running Automatically
Cause: Configuration issue prevents SelectHR batch job from detecting pending records
Batch Job:
SYSTEM - Transfer Successful aCloud Recruitment Candidates
Fix:
Run the batch job manually via SelectHR admin tool
Raise a support case with SelectHR to resolve root issue
Candidate already exists (Duplicate email)
Cause: Email is the unique identifier in SelectHR
Result:
Transfer rejected if candidate already exists
Fix:
Use Rejoiner process in SelectHR
Mark onboarding export as complete in Access Recruit to prevent retries
JSON record not generated (Attachment size issue)
Cause: Attachments (CV, cover letter) exceed allowed size (over 1mb) when converting to JSON
Workarounds:
Create employee manually in SelectHR
Reprocess candidate via Direct Candidate without attachments
Quick diagnostic checklist
If a transfer fails, check in this order:
Data validity (length, characters)
Correct destination system (live vs test)
Batch job status
Duplicate candidate email
Attachment size / JSON generation