Replacement resumes can continue profile processing

When an earlier file becomes current again

If a candidate switches from one resume to another and later returns to the earlier file, automatic processing can start one fresh attempt when the earlier attempt stopped because that file was replaced. This only applies when the current file has no successful profile. Other failed runs, existing successful profiles and your organization’s automatic-processing policy keep their safeguards.

This prevents the supported returning-file blockage. It does not automatically replay an intake message that already stopped retrying or regenerate historical profiles.

A different file can move forward

When you replace a candidate’s resume with a different file, earlier job-application processing could prevent the new file’s automatic profile from starting. The current resume can now move forward when the earlier processing has finished or still refers to the file it replaced.

This applies to automatic profile processing through Talent Inbox, WhatsApp and bulk intake. Your existing organization settings, identity checks and permissions still apply. If RecruitIQ cannot safely confirm which file the earlier processing belongs to, the profile stays held for review. A successful upload does not mean its profile is already complete.

Talent Inbox keeps persistent failures visible

If Talent Inbox saves a resume but cannot start its profile processing, it retries that step. Once the same attachment has failed at least five times and an hour has passed since its first failure, it stops repeating that work and keeps the message marked as an error requiring attention. Later mailbox messages can continue processing.

The saved candidate and resume remain available. Review the candidate and use the existing profile regeneration action when appropriate; after the retry budget is exhausted, the failed step does not restart automatically. Download, parsing and storage failures keep their existing retry behavior.

What this release does not recover

This change prevents the supported replacement-file blockage. It does not regenerate all existing profiles, repair every historical intake failure, or enable automatic AI for an organization. Existing profiles remain available, and checks against starting duplicate profile work remain in place.