Skip to main content

Troubleshooting: Hiring Velocity Filter Showing Unexpected Results

Why a job isn't showing up under the Hiring Velocity filter, or why the count looks wrong.

Written by Amogh Balikai

Who this is for: Anyone getting unexpected results from the Hiring Velocity filter.

A job you expect isn't showing up

Likely cause: The job is closed. Hiring Velocity only evaluates open jobs.

Fix: Check the job's status. If it should be open, reopen it and reapply the filter.

The candidate count looks wrong

Likely cause: Your account's counting mode (Actual vs. Fill Skip Over) is counting stage movements differently than you expect, or a stage movement was recently deleted.

Fix: Check which counting mode your account uses in Settings, and see Fill Skip Overs vs. Actual to understand how it affects this filter's count.

The time window isn't matching what I expect

Likely cause: "Days Since Job Open" measures from when the job was last opened, not its original creation date. If a job was closed and reopened, the clock restarts.

Fix: Check the job's open history, or switch to Last N Days if you want a fixed rolling window instead.

Stage doesn't appear in the dropdown

Likely cause: The stage may not exist on the job's pipeline, or it was renamed or removed.

Fix: Confirm the stage name in the job's pipeline configuration.

Did this answer your question?