Hi ​@Sam_Zuzic and ​@Astr0z0mbie, Excuse me for the wait here. If this is still persisting, please submit a support ticket as this seems to be a bug.Â
Quick checks to narrow it down (so Support/Product can triage fast)
- Confirm whether the candidate is actually moving tabs/groups (vs. disappearing).
In Eightfold, pipeline views can be organized by all statuses vs stage groups, and stage grouping is commonly used to control what appears in each tab. - If you’re using Kanban view, check the Kanban organization setting.
Kanban can be organized by status or stage groups, which can change where the card “lands” after an update. - Try a hard refresh vs full logout/login
Your workaround (logout/login) is effectively forcing a full reload; this aligns with a frontend refresh/caching symptom more than a data-loss symptom. (No doc confirms root cause here, but the symptom pattern is consistent with that.)
Â
What I’d capture for a Support ticket (to avoid back-and-forth)
If you can share these, it’ll make it much easier for Support/Engineering to confirm whether it’s UI-only or a workflow/status mapping problem:
- Group ID / tenant domain
- Requisition/Position ID
- Candidate profile ID
- The exact status transition (e.g., “Recruiter Screen” → “1st Round”)
- Timestamp (with timezone) when you reproduced it
- Browser + version
- Whether you were in Applicants vs Leads pipeline at the time (since behaviors differ by pipeline type).