v2.6.1

Fixed

• is_offline no longer stays stuck true across a logout/login cycle. An agent that went offline (QueueMemberStatus Status 5) while logged into a queue, was then disconnected and later reconnected its WDA and logged back in, kept is_offline: true in GET /queues/agents_status and the queue_agents_status event — nothing cleared the flag after the re-login (only a QueueMemberAdded fires on re-login, and no QueueMemberStatus follows when the device registered before the queue login). Now:
  • is_offline is reset to false when an agent leaves all its queues (full logout / confd dissociation to empty), so a stale value never bleeds into the next login;
  • QueueMemberAdded derives is_offline from the device Status the event already carries (Status 5 → offline), so any (re)join reflects the real device state immediately — including an agent added while its device is still unavailable, which a logout-only reset would miss. Guarded on Status presence so a source that omits it never clobbers a known state.

Covered by four new unit tests (TDD); the QueueMemberStatus Status-5 → offline path (the "agent offline while still in a queue" case) is unchanged.

---

Full changelog: v2.6.0...v2.6.1