Most pages about an ICIMS candidate status not updating are written for job seekers waiting to hear back. This one is for the other side: the recruiter who cannot move a candidate, and the admin who has to work out why.
In our experience the cause is almost always a status option doing exactly what it was configured to do. Here are the seven we check first, and the fix for each.
Where recruiting workflow statuses are configured
Every cause below traces back to one setting. User admins manage statuses at Admin > System Configuration > Applicant Tracking > Workflow > Recruiting Workflow Bins and Statuses.
- Statuses are created globally, then options can be configured per user group using the User Group dropdown. Global Group is the default and affects everyone.
- Each status can carry an auto-launch action, a required flag, a prompt, entrance criteria, and flags such as Hired, Rejected, Interview, Offer, and Stop Portal Application.
- Statuses cannot be deleted. Statuses no longer in use are hidden instead.
That per-group layer is why two recruiters can see different behavior on the same candidate. Always ask which user group the reporting user belongs to.
7 causes of an ICIMS candidate status not updating
ProblemThe recruiter selects the new status, closes the popup that opens, and the status stays where it was.
ImpactCandidates stall between stages, and recruiters report the system as unreliable.
ExampleA status requires Add Note (Rejection), and the recruiter closes the window without choosing a disposition reason.
FixWhen Auto-Launch Required is on, the user must complete the action to update the status. Each action has its own completion rule: for example, Add Note (Rejection) needs a disposition reason saved, Approve Offer needs at least one approver, and Compose Email actions need the email sent. Use the Auto-Launch Prompt to tell users what to do.
ProblemThe status will not accept the candidate, even though other candidates moved into it.
ImpactRecruiters assume the system is inconsistent.
ExampleAn interview status requires a completed screening field that this candidate never filled.
FixEntrance criteria define what a candidate must satisfy before being placed into a status, and admins use them to force candidates through each step. Review the status’s Entrance Criteria Filter, then complete the missing step or adjust the criteria.
ProblemCandidates already in the status can be moved out, but nobody can move anyone in.
ImpactA stage of the workflow quietly stops being used.
ExampleA status was locked during a workflow redesign and never reopened.
FixA read-only status is locked: new candidates cannot be moved into it, while existing candidates remain viewable and can move out. Clear Read Only if the status should still be used, globally or for the right user group.
ProblemA recruiter cannot find the status in the dropdown, or sees it labeled Hidden with an ID.
ImpactRecruiters improvise with the wrong status, which skews reporting.
ExampleAdmins hid an old status for one region’s group, and a recruiter moved teams.
FixA hidden status is retired: it does not appear when advancing or rejecting, and cannot be used in searches or reports. Users it is hidden from see it as Hidden (List Node ID). Check the status options for the recruiter’s user group, not only the Global Group.
Candidates stuck between statuses?
We will review the statuses your recruiters report on the call, check their options by user group, and tell you which of these seven causes applies.
Book a discovery callCauses 5 to 7: flags, candidate labels, and integrations
ProblemA recruiter says a status disappeared; it is actually listed elsewhere.
ImpactTime lost and statuses chosen by guesswork.
ExampleA status was given the Rejected flag during cleanup and moved from Advance to Reject.
FixThe Rejected flag decides which dropdown a status appears in: statuses with the flag show under Reject, and every status without it shows under Advance. Confirm the flag matches how the status is used.
ProblemA candidate says their application still shows an old stage, while ICIMS shows them further along.
ImpactCandidate complaints and recruiter time spent explaining.
ExampleInternal labels were renamed, but candidate-facing labels were not.
FixThe label users see and the status information candidates see are configured separately. ICIMS documents candidate-facing status labels in its article on configuring candidate-facing status information in System Configuration. Align the two whenever you rename statuses.
ProblemA background check clears or a workflow transfer runs, and the status does not change the way the team expected.
ImpactCandidates wait in the wrong stage.
ExampleA Prime Background Screen setting points at a status that was later hidden.
FixIntegration-driven moves follow their own settings. For example, Prime Background Screen Automatic Workflow Status Update settings default to no status, and an update does not happen if the target status or bin is hidden from the integration user group. Submit to New Workflow actions also do not remove the candidate from their current workflow. Our ICIMS background check integration setup guide covers the screening side.
Status options versus workflow rules
Status options control what happens when a user moves a candidate. Workflow rules automate moves and actions based on conditions. If a status was supposed to change automatically and did not, start with our ICIMS workflow rules not triggering guide. If a user tried to change it and could not, the seven causes above are the place to look.
| Symptom | Most likely area |
|---|---|
| User selects a status and it does not save | Required auto-launch action or entrance criteria |
| Status missing from the dropdown | Hidden for the user group, or Rejected flag placement |
| Cannot move anyone into a status | Read Only |
| Candidate sees an old stage | Candidate-facing status labels |
| Expected automatic move did not happen | Workflow rules or integration settings |
A five-minute admin checklist
- Ask which user group the recruiter is in, then open Recruiting Workflow Bins and Statuses with that group selected.
- Find the target status. Check Hidden, Read Only, and the Rejected flag.
- Check the auto-launch action and whether Auto-Launch Required is on.
- Open the Entrance Criteria Filter, if one exists, and compare it with the candidate’s profile.
- If an integration should have moved the candidate, check that integration’s status settings.
How to prevent status problems
Offer statuses deserve special care because they often carry Approve Offer or Offer Wizard actions. Our ICIMS offer management setup guide walks through them. For teams that want someone else to own this upkeep, our ICIMS managed services cover ongoing workflow administration.
Frequently asked questions
Keep candidates moving
Book a discovery call and we will walk your recruiting workflow configuration with you, then hand back a fix list your team can own.
Book a discovery call
