Skip to main content

​
What you’ll accomplish

You will hand one Queue Unit to an active Edge and understand how Layarva prevents the Cloud and Edge from issuing conflicting tickets.

​
Prerequisites

  • An active paired Edge.
  • A configured Queue Unit.
  • Queue management permission.
  • A trusted Edge clock.

​
Grant authority

  1. Open the Queue Unit Overview.
  2. Find Edge server.
  3. Select Hand over to Edge.
  4. Choose the active Edge and confirm.
  5. Verify the authority holder, epoch, lease freshness, and configuration version.
One Edge can hold several Queue Units in the same building. Authority is assigned per Queue Unit.

​
Lease and epoch

Edge authority is a renewable 120-second lease. A worker can expire or reconcile it if the Edge stops synchronizing. Every handover advances the Queue Unit’s epoch. The epoch is stored on the Queue Unit so a removed authority record cannot accidentally make an old Edge trustworthy again. The assignment row is locked while changing authority, preventing two Admins from handing the same Queue Unit to different Edge devices at the same time.

​
Configuration synchronization

Any Queue configuration change that Edge must learn increments edgeConfigVersion. A version mismatch forces a complete bootstrap refresh instead of a fragile stream of deltas.

​
Ticket number blocks

Edge normally reserves blocks of 100 ticket numbers, with a minimum requested block of 10. Reserved numbers are never reused after a conflict or outage; a gap is safer than issuing the same customer number twice.

​
Reconciliation

When the WAN returns:
  1. Edge renews authority and uploads operations.
  2. The Platform applies idempotent operation IDs.
  3. Conflicts are recorded for administrative review.
  4. Queue activity and reports show reconciled events.
  5. Platform webhooks are emitted in applied order.
Authority can be released because of an operator action, reassignment, expiry, device release/disablement, or Queue Unit archival.