InferOwlInferOwl
Jobs and daily work

A pipeline move is blocked or rolls back

Understand transition requirements and confirm the saved state before treating an application as moved.

Everyday work3 min readRecruiting workflows

Before you begin

Access to the job and its application. · Move candidate stage permission.

Work through this checklist

1. Read the transition message

Open the intended job pipeline and confirm the candidate and destination stage. Read the blocker shown by the board. A visual card movement can be reversed if the save fails.

2. Complete the stated requirement

Depending on the stage configuration, InferOwl can require a candidate email, phone, finalized resume, qualified screening, or readiness. Complete the actual requirement before trying the move again. Do not mark work complete merely to clear a blocker.

3. Provide a reason when asked

Some destination stages request a transition reason. Explain the real recruiting event that justifies the move. Cancel if you do not yet have the information needed to support it.

4. Respect the configured workflow

A pipeline can limit allowed next stages or prevent movement out of a terminal stage. Ask the workspace owner to review an unexpected rule; do not change shared rules simply to force one card through.

5. Confirm the saved state

Read the success or rollback notice. If the result is uncertain, refresh the pipeline and inspect the application’s current stage before trying another move.

If you still need help

For a persistent failure, report the job context, source and destination stages, approximate time, and exact non-sensitive error text. Do not tell teammates the stage changed until the board confirms it.

Read the complete product guide

Was this guide helpful? Send feedback to the team.