Check sync and recover saved work

A record can be saved on your device while its delivery to Geova Cloud is still pending. Check the save message and synchronization status before handing work to another team member.

Before you start: Keep the original device and project available. For hosted sync, use the intended signed-in workspace with connectivity and the access needed for the saved operation. Avoid clearing application data, reinstalling, or deleting the project while unsent work remains.

Choose the right handover

Your project or task	Use
Hosted project with queued changes	Sync Inspector and the recovery steps below
Local project that stays on the device	Local saving; it does not automatically upload to Geova Cloud
Transfer between nearby field devices	Field Gathering, using its session code and transfer result
Give a file to another application	Export and inspect the result using the format preservation reference

A nearby transfer or file export is a separate handover. Its success does not confirm that a hosted queue has finished.

1. Open Sync Inspector

Tap the app's sync status control to open Sync Inspector. Review:

• Connectivity: whether the device reports Online or Offline.
• Queued Changes: work still waiting locally, including standard changes and related-data operations.
• Last Sync: the latest attempt, its time, and any reported problem.
• Queue Detail: the oldest standard changes, useful for identifying work that stays pending.

Online indicates connectivity, but access or service errors can still prevent delivery. A zero queue means no known queued work remains; direct cloud saves do not appear in the queue. If Relational status unavailable is shown, Mapplex cannot confirm an all-synced state.

2. Send eligible changes

1. Confirm connectivity and access to the intended workspace.
2. Select Sync N Changes, where N is the number currently eligible.
3. Keep the app open while it works, especially for a large queue.
4. Review Last Sync, the remaining count, and any attention message.
5. Check the expected records from the receiving team member's view before declaring the handover complete.

Some changes may finish while others remain pending. Read the remaining status instead of assuming the whole attempt failed or succeeded.

3. Interpret a waiting or blocked status

Status or message	Meaning and next action
Offline	Changes remain on the device. Reconnect before hosted retry
Standard changes waiting for automatic retry	The app has delayed another attempt. The normal sync action can retry eligible standard changes immediately
Ready under Relational operations	Saved related-data work is eligible for sync
Backoff	Related-data delivery is waiting before another attempt; check again when it becomes eligible
Dependency wait	An earlier required operation must finish first. Check the earlier work; do not create replacements
Needs attention	The request needs review. Use the matching recovery path below
Relational status unavailable	Refresh after restoring connectivity and session access; do not treat the visible count as a complete all-synced result

Standard changes paused after repeated failures

“Quarantined” means automatic and normal manual retries have been paused for those changes.

1. Read the error and check connectivity, sign-in, and workspace access.
2. After correcting the cause, choose Retry N quarantined changes.
3. Review the new result and remaining count.

Repeatedly pressing normal sync does not release quarantined changes.

Related-data requests that failed access or delivery checks

Use Retry saved requests after checking the session and access. This reuses retained requests rather than creating duplicate records. Review the Reviewed …; synced … result and select Check next batch if offered.

This control does not resolve validation conflicts by overwriting them. Requests still needing attention remain saved. If a message says the server refused a request, review the reason and the original request before retrying.

Recover a hosted update or archive

Use this path when an edit or archive was submitted but its final state on the device is uncertain. It is available through the related-data workflow when the corresponding hosted operation is enabled.

1. Open Data & Sync and the related-data panel.
2. Under Hosted update recovery, choose Review pending hosted updates. For archives, use Hosted archive recovery → Review pending hosted archives.
3. Find the affected record and inspect the operation's phase, attempts, retry time, and last error.
4. Choose Check status safely first. This checks the retained operation instead of starting a new edit or archive.
5. If recovery offers Review retry, inspect that review. Select Confirm exact retry only when you intend to retry the same saved operation.
6. Review the outcome, reload the table, and verify the record.

A hosted operation may already be accepted while the device still needs to bring its local copy into agreement. That is why a second edit or archive is not the first recovery step.

If current record or form information is stale, or the review cannot establish a safe retry, follow the displayed result and have the project manager review it. Recovery does not authorize a different edit or bypass access controls.

Recover an unresolved local relationship

An unresolved link means Mapplex cannot connect the saved relationship to its exact required records. Use Quarantined link recovery in the related-data panel for a local project.

This requires Owner or Admin access and an online, fresh membership check, even though the project is local.

1. Select Refresh quarantine.
2. Inspect the link and its dependency information.
3. Use Retry exact dependencies when the original relationship, parent, and child are available. Confirm the exact saved IDs.
4. Use Discard unresolved draft only when the owner or administrator has decided to abandon that link.

Discarding retains the link's identity and audit history as a “tombstone,” meaning a recorded discarded item. It is not a command to delete the parent or child records.

If the result is still unclear

Keep the device's saved work. Give support the workspace and project names, action performed, approximate time, visible error or operation reference, and whether the problem is standard sync, related-data delivery, an update, or an archive. Share only the record details needed to investigate.

Completion check: No applicable pending or attention state remains, related sync status is available, and the intended recipient can see the expected result. For an offline field preparation routine, use Prepare for offline work.