# X_OFFLINE_QUEUE_ABANDONED

## Means

a write was queued after its page changed principal

## Typical cause

a write reached `OfflineQueue.enqueue()` on a queue `abandon()` had already ended — the page moved to another principal (a sign-out, a sign-in as someone else) while the write was being queued. It was NOT stored and will never be sent: a write issued under one session must not leave under the next. Raised to the caller so the loss is never silent; call the mutation again under the current session

## Fix

`x errors explain X_OFFLINE_QUEUE_ABANDONED --json`

[Realtime](/error-codes#realtime)
