Add a candidate batch and see the updated job count

Track your selection

Updated September 19: the current Candidates list adds selected candidates one at a time, showing one progress indicator and confirmed counts such as 1 of 6 added. If an assignment is updated, skipped, or fails, the counter says processed and shows the separate outcomes instead of calling everything newly added. Other bulk assignment surfaces still submit one batch.

Sequential progress may take longer for large selections. Keep the page open while it runs. If a connection or request fails, RecruitIQ stops sending the remaining candidates, preserves confirmed results, and asks you to check the job before retrying an unconfirmed assignment. Failed and unattempted candidates remain selected.

The completion summary still separates newly added candidates, updated assignments, candidates already on the job, and errors. A problem with one candidate remains visible in the batch result instead of being hidden by the successful additions.

Refresh the affected pieces

A completed assignment returns the job’s authoritative candidate count. RecruitIQ applies that count to the prepared Jobs row immediately, advances the organization’s Jobs-list version, and refreshes the job pipeline and Activity fragments connected to the assignment.

The selected candidate rows also update their Pipeline count when a new job link is created. Opening the job or candidate afterward uses the refreshed fragment rather than waiting for an unrelated page cache to expire.

Preserve assignment safeguards

Existing organization checks, workflow validation, duplicate detection, recruiter notifications, and candidate-level error reporting still run for every candidate. Sending one batch does not bypass those controls or silently add a candidate twice.

Some batches can still take longer when external notifications or connected application updates are required. The batch reduces repeated setup and stale follow-up reads; it does not treat an unfinished assignment as complete.