Platform
Workbench Sync
How field work captured offline is validated and synced back to the server.
Last updated
Workbench sync allows field users to continue working during unstable connectivity and submit changes when a connection is available.
How it works for users
In the workbench, users can:
- keep working with local-first behavior
- view sync activity and queue state
- retry failed items
- see accepted vs rejected outcomes
Sync visibility is provided inside the workbench experience.
Current sync scope
The current sync pipeline handles key field actions including:
- customer creation
- account creation
- transaction intent submission
Server-side validation and control
Incoming sync actions are not accepted blindly. The server applies:
- idempotency checks
- permission checks
- workflow policy checks
- feature-level validation
- custom-field processing where required
This keeps offline capture aligned with the same business rules used for online actions.
Result states and support handling
Each queued action ends in a visible state such as queued, syncing, synced, failed, or rejected.
For support and operations teams:
- Check the sync panel outcome first.
- Resolve data or permission issues for rejected items.
- Retry failed items after correcting the cause.