Drafts, queues, synchronization, and recovery
How local work moves to the server and how to recover safely.
Workbench separates editable local Drafts from submitted queue items and from server records.
Local lifecycle
- Draft: editable only on this device for this user.
- Queued: validated locally and waiting for a connection or sync turn.
- Syncing: currently being submitted.
- Synced: accepted idempotently by the server and linked to its server record.
- Failed: retryable transport, authentication, throttling, or service failure.
- Rejected: a non-retryable permission, reference, or validation failure; correct the retained Draft before resubmitting.
- Returned to draft: explicitly reopened for correction where the journey supports recovery.
Use the Sync panel
On Home, review Draft, Queued, Failed, and Synced counts plus Network, Engine, Storage, last-online, and last-sync indicators. Sync now is enabled only while online and local storage is ready. Retry failed requeues retryable failures; it does not make a fatal rejection valid.
Expand an item to capture its action, timestamps, queue ID, Account flow where available, and error details for support.
Safe recovery order
- Preserve the Draft; do not reset local storage while unsynchronized work exists.
- Restore a reliable connection and sign in again if authentication expired.
- Refresh authorization and the relevant reference package.
- Retry only a Failed item whose underlying transient cause is resolved.
- For Rejected, return/review the Draft, correct its fields or permission problem, and submit a changed payload.
- Confirm the server record and a current Last sync time before clearing local data or logging out.
Every queue item carries an idempotency key, so retries of the same accepted action do not intentionally create a duplicate record.