This page describes steps to troubleshoot issues you might encounter when working with the positions pipeline.

Error when trying to access the positions pipeline

Cause: This error typically occurs due to limited permissions. Recruiters or hiring managers may not be able to view positions because they lack access to all pipelines.

Solution: Work with the internal Admin team to assign them as a member of the hiring team with appropriate permissions.

Error when trying to reject candidates

Cause: If candidates have not applied for the position or haven't answered mandatory application questions, the reject action will display an error.

Solution: Ensure that candidates have applied and completed all necessary application questions before attempting to reject them.

Unable to advance a candidate to a position

Cause: This issue can arise if the position is no longer active or posted.

Solution: Verify the status of the position. If it's not active or posted externally, resolve the issue before attempting to advance candidates.

Unable to view the job on the careers page

Cause: The job may be posted only for internal users, resulting in an error when clicking on the external job link.

Solution: Ensure that the job is posted for both internal and external users to resolve the error on the careers page.

Error when trying to open the job on the careers page

Cause: The job may be posted only for internal users, causing an error when accessing the external job link.

Solution: Adjust the job settings to allow access for both internal and external users to resolve the error.

Option to "Advance Stage" is missing

Cause: Permissions or roles for the account may need adjustment.

Solution: Reach out to Eightfold Admin to discuss and decide on the appropriate permissions or roles for accessing the stage advancement tab.

There is a discrepancy in numbers being shown on the Candidates tab and the ATS Stage filter within it.

Cause: When you bulk perform any action on the candidates in the pipeline, there might be a slight lag due to which you could see different numbers.

Solution: Users should avoid executing the action multiple times (for example, selecting a group of candidates to send an email to, and then selecting another group for the same email).

Since these are bulk activities, it is recommended to leave a few minutes between actions to avoid performance issues.

Candidates in the APPLIED stage were selected to receive a thank-you email, and the system mistakenly sent a rejection email to a candidate in the Integrity Check stage

Cause: The candidate was rejected for the specific position hence the rejection email was sent post the candidate was moved to rejection stage.

Solution: Contact the candidate and ask them to disregard it.

Candidate is an employee but did not appear in the internal candidate filter (employees)

Cause: The candidate is termed as past employee, due to which the user is not filtered while applying the internal user (employee) filter in the position pipeline page.

Solution: Reach out to the internal Admin team and change the status to employee.

"Error Changing Application Stage: Signature Required For Internal Candidate As Per Field Override, For Templateid 2682, With The Index 0"

An error is encountered while advancing a candidate.

Cause: This error occurs when the application for the candidate is not created by the Eightfold system. The system that generated their application omitted the required answers to certain questions, which is causing the error.

Solution: Add the required fields to the candidate's profile in SuccessFactors and then try advancing the candidate.

Tracking candidates in Communities

The basic rule Once you add a candidate profile to a Community, Eightfold tracks what happens to them next.

What gets tracked - If they get rejected - they show up in the "Rejected" list - If they get hired - they show up in the "Hired" list - If both happen - they show up in both lists

Example Let's say John joins a Community on November 19, 2025. After that: - He applies for Job A and gets rejected - He applies for Job B and gets hired

Result: John appears in both the "Rejected" and "Hired" lists because both things happened after he joined the Community.

Important: The system only counts what happens after someone joins the Community.

Why this matters This helps you see the complete journey of each candidate in your Community - whether they had one outcome or multiple outcomes with different positions.