Using Emplyr · Android and offline work
How to resolve Android conflicts and rejected changes
Review competing edits without discarding valid queued work.
On this page
Before you start
- Keep the device and its app data available. Connect online and identify the exact affected process/record.
Follow these steps
- Open Sync and check Needs attention and Conflicts. Select/open the affected record through its process.
- If the server rejected a change, read the reason, correct the named field or request the required access/state change, then use the record’s retry/save flow.
- For “This draft changed on the server”, compare the server version with your local work and involve the record owner when both contain useful changes.
- Use Keep server only when the server version should win. Use Save local as new draft only when a separate new draft is the intended business result.
- Use Retry after review when you have reviewed/corrected the competing change and the process offers that path. Wait for the new sync result.
- Confirm the resolved record on the server and check the remaining queue. Send the safe record reference and message to your administrator if the conflict cannot be reconciled.
What you should see
The conflict has a deliberate resolution, with the correct record retained and no accidental duplicate created.
If something goes wrong
You are unsure which version is correct
Stop and ask the record owner before choosing a resolution.
A block is about subscription/placement
Use the paused-profile recovery guide; the local work remains stored and the block is retryable.
The device is lost or damaged
Notify your organisation’s administrator promptly for session/device response. Do not share your password to help someone recover it.