Queue reprocessing reference
This article is a reference companion to Understand queue reprocessing. It provides a detailed breakdown of what queue reprocessing recalculates, how auto-purge integrates with reprocessing, the concurrency safeguards that prevent duplicate cycles, and the audit information maintained for each cycle.
Note: For a conceptual introduction to queue reprocessing and when it occurs, see Understand queue reprocessing.
Audience: Managers and administrators who want a detailed understanding of reprocessing behavior to troubleshoot queue accuracy or optimize settings.
On this page
- Before you begin
- What reprocessing recalculates
- Auto-purge integration
- Concurrency safeguards
- Multi-segment handling
- Provider assignment locking
- Scheduled-service guest prioritization
- Audit trail
- Tips
- Troubleshooting
- Related articles
Before you begin
- Queue reprocessing requires the Reschedule queue based on resource availability setting to be enabled at the center level (Configuration > Appointments, Essentials section of the center page; the row appears once Operate appointment book in Queue mode is on), with the queue enabled at both the organization and center levels.
- The Enable Admin Queue setting must be active at the organization level, and Operate appointment book in Queue mode must be enabled at the center level.
Note: When Reschedule queue based on resource availability is disabled, the queue does not automatically recalculate times or reassign providers after state changes. Wait times and positions remain static.
What reprocessing recalculates
During each reprocessing cycle, the system performs the following in order:
- Identifies appointments needing assignment. The system finds all waiting appointments that are missing a start time, end time, or provider assignment.
- Orders appointments by queue position. Appointments are sorted by their queue join time (check-in time), with earlier check-ins first. When Prioritize guests with scheduled services over walk-in guests is enabled, scheduled-service guests are placed ahead of walk-in guests in the resolved ordering.
- Calculates cumulative service times per provider. For each provider, the system adds up the durations of all assigned services to determine when the provider will next be free.
- Assigns next available time slots. Each unassigned appointment receives an estimated start time based on the next available provider slot.
- Updates provider assignments (when Assign therapist based on idle time is enabled). The provider with the highest idle time who qualifies for the service is assigned to appointments that need one.
- Skips locked assignments. Appointments where the provider assignment is locked retain their current provider; only time recalculation applies.
- Updates queue positions. All waiting guests receive recalculated position numbers.
- Updates the center wait time. The estimated wait time displayed at the top of the queue is recalculated.
- Triggers notifications. Guests who become next in line, reach a position threshold, or fall within a wait time threshold receive their configured notifications.
- Broadcasts updates. All open queue screens refresh automatically to reflect the updated information.
Auto-purge integration
When the Enable automatic purge of no-show guests from queue center setting is active, the auto-purge process runs as part of the reprocessing cycle. After recalculation completes, the system evaluates each waiting appointment against its source-specific timer:
| Appointment source | Timer setting |
|---|---|
| Walk-in | Set an auto-delete timer limit for walk-in guests (in minutes) |
| Online check-in (guest confirmed in store) | Online checkin and guest in store timer limit (in minutes) |
| Online check-in (guest not confirmed in store) | Online checkin and guest not in store timer limit (in minutes) |
Appointments that have exceeded their timer are marked as no-show. This triggers another reprocessing cycle to incorporate the newly freed-up time.
Auto-purge requires both Enable automatic purge of no-show guests from queue (center level) and Reschedule queue based on resource availability (center level) to be active. If either is disabled, no automatic no-show marking occurs.
Note: When a guest's appointment is auto-purged, staff can bypass the remaining timer using the bypass action. The bypass replaces the appointment's remaining purge timer with the configured Bypass purge timer limit (in minutes) value — it does not add to the remaining time. For details on managing no-shows and bypass, see Manage no-shows and auto-purge.
Concurrency safeguards
To prevent duplicate processing during rapid-fire state changes, the system enforces the following:
- Reprocessing lock — Before starting a cycle, the system acquires a per-center processing lock. If the lock is already held by another in-progress cycle, the new request is skipped and a retry is scheduled automatically.
- Cooldown validation — The system checks whether any main appointment at the center was updated very recently before starting a new cycle. If the check fails, the cycle is deferred to avoid conflicts with in-flight changes.
These safeguards ensure the queue stays accurate and responsive without consuming excessive resources during peak hours. Staff do not need to take any action when a cycle is skipped — the queue updates automatically when the current cycle completes.
Multi-segment handling
For appointments with multiple service segments, the reprocessing engine processes each segment independently:
- Each segment can have a different provider and a different estimated start time.
- Completing one segment does not affect the scheduling of other segments on the same appointment.
- The engine assigns time slots for each segment separately, which allows segments to be handled by different providers or scheduled back-to-back with the same provider.
Important: When a multi-service visit is started as a whole from the queue, services are scheduled sequentially — each service starts only after the previous one ends. This is distinct from starting individual segments from the Appointment Book, where each block updates based on its own actual start time and sequential calculation does not apply.
Provider assignment locking
Individual appointment queue records can have their provider assignment locked. When a provider assignment is locked for an appointment:
- The reprocessing engine does not change the assigned provider for that appointment.
- Time recalculation still applies — the appointment's estimated start time may shift based on changes elsewhere in the queue.
- Locking is useful when a guest has a strong preference for a specific provider and staff want to guarantee that assignment is preserved across reprocessing cycles.
To lock a provider assignment for an appointment, expand the queue card and set the assignment through the edit flow. For step-by-step instructions, see Assign providers in the queue.
Scheduled-service guest prioritization
When Prioritize guests with scheduled services over walk-in guests is enabled at the organization level, the reprocessing engine adjusts queue ordering so that guests with pre-booked (scheduled) services are placed ahead of walk-in guests, regardless of check-in time.
This setting affects only the ordering computed during reprocessing — it does not change the check-in process or the visual position numbers guests see before a reprocessing cycle runs.
Important: This setting controls scheduled-service versus walk-in priority. It does not create a call-ahead prioritization system based on arrival time or phone reservation.
Audit trail
After each reprocessing cycle, the system logs all provider and time changes for the affected appointments. This audit data includes:
- The old and new provider for each appointment where the provider changed.
- The old and new estimated start time for each appointment where the time changed.
This information is available through the appointment history and reporting tools and helps managers review how the queue was managed throughout the day.
Tips
- Enable Reschedule queue based on resource availability at the center level before expecting automatic time recalculation. Without this setting, wait times and provider assignments remain static after state changes.
- Use provider assignment locking for guests with strong provider preferences. Locking preserves the assigned provider across all reprocessing cycles while still allowing wait time recalculation.
- Configure source-specific auto-purge timers to match your guest flow patterns — walk-in guests typically warrant shorter timers than online check-in guests who may be en route.
Troubleshooting
Wait times are not updating after a service is completed. Confirm that Reschedule queue based on resource availability is enabled at the center level under Configuration > Appointments. If the setting is off, the queue does not recalculate automatically. Also verify that Operate appointment book in Queue mode and Enable Admin Queue are both active.
A provider keeps getting reassigned even though staff set a specific provider. The provider assignment may not be locked for that appointment. Expand the queue card, confirm the provider assignment, and lock it so the reprocessing engine preserves it. See Assign providers in the queue for steps.
Walk-in guests are being marked as no-show too quickly. Check the Set an auto-delete timer limit for walk-in guests (in minutes) value under Configuration > Appointments > Queue (center-level Wait times page). Increase the timer to give walk-in guests more time before auto-purge triggers. If auto-purge should not apply to your center, disable Enable automatic purge of no-show guests from queue at the center level.