🔎 Troubleshooting Common Issues
| What might be wrong | How to fix it |
|---|---|
| Wrong evaluator selected in the automation rule | Open the assessment step → Automation side panel → edit the rule and verify the evaluators selected under Auto-assign evaluator. |
| Automation rule applied to the wrong assessment step | Confirm the rule is created for the correct assessment step. Rules do not apply across steps. |
| Conflicting automation rules | Check Current Automations for multiple active rules that include evaluator assignment and deactivate unnecessary ones. |
| Evaluator manually changed after auto-assignment | Verify whether the evaluator was reassigned manually after the automation ran. |
| Candidate already had an evaluator assigned | If an evaluator was previously assigned, the rule condition Evaluator not assigned may not behave as expected. Remove existing assignments and retry. |
| Rule edited after assignment occurred | Automation rules do not retroactively update evaluator assignments. Changes apply only to future candidates or invites. |
| Assessment invite resent after rule update | Resending invites after modifying rules may trigger a different evaluator assignment if rule conditions differ. |
Additional Tips
- Review Current Automations regularly Always check the Current Automations section to ensure only the intended rules are active.
- Test with a fresh candidate Add a new candidate to the assessment step and send the assessment invite to validate correct evaluator assignment.
- Use clear naming or documentation When multiple recruiters manage the same workflow, document automation intent to avoid accidental evaluator changes.
- Avoid overlapping rules Keep evaluator assignment logic simple to reduce unexpected behavior.