Qlinic Queue Recall Logic Dashboard

Phase 2 queue behavior showing how skipped tokens move to On Hold, wait through three subsequent calls, and then return automatically to service.

Total Tokens
Skipped to On Hold
Exact 3-Token Recalls
Final No-Shows
Recall rule

When a patient is absent, the token is not discarded. It changes state to On Hold, the queue continues serving the next tokens, and the skipped token is auto-recalled after exactly three later calls.

1

Skip

The token is called and then marked absent, shifting from Now Serving into an On Hold state.

2

Wait Through Three Calls

The queue keeps moving while three later tokens are called and processed in order.

3

Auto-Recall

After the third intervening call, the skipped token re-enters service automatically for its final outcome.

 Now Serving  On Hold / Skipped  Completed  No-Show
Highlighted skipped-token journeys

This panel traces the two tokens that entered On Hold and shows how their recall paths diverged after returning to service.

Queue state timeline by token
Gantt-style view of state transitions across the session, including the return of A-02 and the final No-Show for A-06.
Three-token auto-recall path for skipped tokens
Each skipped token remains On Hold until three subsequent tokens have been called, then the recall fires on the next step.
Final token status summary
Token Final Status Notes Recall Path