Skip to content
English
  • There are no suggestions because the search field is empty.

Sending a candidate to iTrent and fixing sync problems

How HR sends a hired candidate to iTrent, follows the sync, and cancels, retries or fixes one that fails.

How HR sends a hired candidate to iTrent, follows the sync, and cancels, retries or fixes one that fails.

This is for HR and System Admin users. The iTrent connection must already be set up by a System Admin (see "Setting up the iTrent integration") and the candidate needs a submitted application. Anyone who can open the candidate can read the sync history, but only HR and System Admin users get the buttons.

Send a candidate to iTrent

Open the candidate, go to the Onboarding tab, and select Push to iTrent. If your organisation has switched onboarding off, the tab is named HRIS Sync instead. The button shows Pushing... while the sync runs. The card only appears while an HRIS connection is switched on.

If Auto-trigger on hire is on, Recruit starts the sync itself when an application moves into a stage of the Hired type, so you only need the button for candidates it has not sent.

Recruit sends the People map first and waits for iTrent to reply. Each later map goes only after the one before has been accepted.

Follow a sync

The history sits under the button, headed HRIS Synchronisation Activity. Each attempt has a status badge, a step count such as 3 / 8 with a progress bar, and any error in a red box. Open the arrow to see each step with its time. Steps are named after the maps, such as PEOPLE, EMAIL and MOBILE. While a sync is running the page refreshes every few seconds.

  • Pending: created, nothing accepted yet.
  • In progress: iTrent has accepted a map and Recruit is moving through the rest. It stays here until iTrent replies.
  • Complete: every map has been handled.
  • Failed: a step was refused or could not be sent. The error says why.
  • Cancelled: stopped by a person. The note reads "Manually cancelled by user".

System Admins can also see every candidate's syncs in one list. Go to Settings, then Integrations, and scroll below the cards to HRIS Synchronisation Activity. Filter with All, Complete, Failed or Cancelled. The columns are Candidate, Provider, Status, Progress, Triggered by (manual or auto), Started and Completed, with Previous and Next buttons at 20 rows a page. The Candidate column shows a reference code, not a name. Select a row to open the candidate, and use the eye icon (View error details) on a failed row to read the error. An empty list reads "No synchronisation activity yet."

Cancel and retry

Select Cancel beside a Pending or In progress sync to stop it. The message "Sync cancelled successfully" appears. Anything iTrent has already accepted stays in iTrent.

Select Retry push on a Failed sync, or on a Cancelled one from the button at the top of the card. Recruit keeps the old entry for the record and starts a new sync from the first map, not from the step that failed. Each sync can be retried three times, after which Recruit refuses with "Maximum retry count (3) exceeded". A sync that stays In progress is waiting on iTrent, so cancel it and retry once you have checked with your iTrent administrator.

Errors and what to do

The text in the red box is either Recruit's message or iTrent's own.

  • "Failed to build PEOPLE" saying required fields are missing: none of the People fields had a value for this candidate. Check the candidate's details and the mappings.
  • "Failed to send PEOPLE map:" followed by "iTrent authentication failed": the API Username or API Password is wrong, or the iTrent account is locked. A System Admin corrects the details in the Configure iTrent dialog, then you retry.
  • "iTrent server error" with a number, "after retry": iTrent was unavailable. Recruit already tried twice, so retry later.
  • "iTrent request failed" with a number, or "iTrent rejected" with a reason: iTrent refused the data. The reason is iTrent's, for example a missing mandatory field.
  • "Next map send failed:" followed by a reason: the People map went through but a later one could not be built or sent.
  • iTrent's own reply text, or "Unknown error (no ErrorDescription in response)": iTrent replied that a step failed. Fix the data in iTrent or in the mapping, then retry.
  • "A draft application cannot be pushed to the HR system": the application has not been submitted.

To change what is sent, see "Choosing which details are sent to iTrent".