QFieldCloud Sync Failed: Protect and Upload Field Data

When QFieldCloud sync failed appears during fieldwork, preserve the device holding the edits before downloading another project copy. Identify whether the failure is uploading changes, applying them in the cloud, or preparing a download: those stages run in different places and need different remedies.

Key Takeaways:

• Keep the original edited project until its changes are verified in the authoritative data.
• An uploaded change is not necessarily an applied change.
• A phone's network comparison cannot repair a cloud worker's database connection.
• Check a known record in a separate downloaded copy after successful application.

What should you preserve when QFieldCloud sync failed appears?

Finish the current edit and save it using your project's normal workflow. Record the device, QField version, project, affected layer, and a record identifier that you can safely recognize later. Stop collaborators from changing the project structure while the recovery is being coordinated; a new schema can complicate pending offline edits.

Create a backup using the storage or export method supported for your device and project. Confirm that the backup contains the relevant local project and data, rather than only the desktop .qgs file. If you cannot identify where the pending edits are stored, ask the project administrator before uninstalling QField, clearing app storage, or replacing a local folder.

The general device troubleshooting guide is useful when the phone also fails in other applications. For this problem, keep a more specific boundary: the device holding the offline edits is the upload source. A different computer reaching QFieldCloud does not prove that those edits left the phone.

Observation	Responsible stage	Safe next check
No new change appears in the cloud	Device upload or project access	Original device and upload result
Change appears but remains pending or failed	Cloud application	Change status and job log
Packaging fails	Cloud download preparation	Package job and source availability
Another copy lacks the edited record	Applied data or download freshness	Record identity and package time
Different users edited the same feature	Conflict resolution	Project owner's merge policy

Step 1: How do you preserve the unsynchronized edits?

Work from the original device and keep its project available. Document the latest edit and any attachments that should travel with it. Use a meaningful record ID or an existing observation, not a new fake feature inserted into production data only to test networking. If the local app can display the edited value, record that value securely for later verification.

Do not delete and download the project as an opening troubleshooting step. That changes the copy you are trying to rescue and can remove the evidence of what is missing. Likewise, do not clear application data or reinstall before the pending edits and attachments have an independently checked backup.

Offline editing in QFieldCloud produces changes for modified features, while other layer modes can access an online source directly or expose file data as read-only. Check the actual layer action; a directly accessed database layer is not automatically protected by the offline-change workflow discussed here. ［1］

Ask the owner to preserve a compatible project definition until everyone's pending changes are reconciled. Record whether fields, layers, or constraints changed after the phone's copy was downloaded. A stale schema may be the relevant cause even when the upload connection is healthy; do not try to repair it by repeatedly sending the same edits.

Step 2: Where does the QFieldCloud upload error occur?

Read the operation you started: pushing edits, synchronizing, or downloading a project. The first-project tutorial describes pushing changes from QField and synchronizing the project, but the screen's broad sync label does not identify the exact failed stage. Keep the actual action and first reported error in the evidence record. ［2］

Separate three questions. Did the phone deliver its changes? Did the cloud apply them to the original source? Did a later download package contain those applied changes?

Answer each one independently instead of treating a progress bar reaching its end as full recovery.

Inspect the project's Changes and Jobs information through an authorized account. Record the affected change and job identity privately. If the cloud already has the change, that is evidence against retrying the phone upload as the only remedy. If no change arrived, first verify the correct project and account before concluding that transport failed.

The cloud-storage synchronization checklist explains the broader distinction between local and remote copies. Here, the decisive objects are QField changes, project layer actions, and cloud jobs. Do not replace those checks with generic advice to delete caches or upload a whole folder again.

Step 3: What do the cloud jobs report?

QFieldCloud distinguishes project processing, packaging, and applying deltas. Use the job type and its result to decide which owner should act. A successful project-processing job alone is not confirmation that the intended field changes were applied, and a failed package does not necessarily mean the phone failed to upload. ［3］

For an existing pending job, inspect its status before pressing the same action repeatedly. Record the first useful error and timestamp. A cloud worker may fail while reaching a database or another source; changing the Android device's exit changes the device connection, not that worker's outbound network.

A conflict or incompatible layer definition requires the project owner's decision. Do not overwrite another user's feature, rename fields on the phone, or force a re-application without understanding which edits should prevail. Keep both the local evidence and the cloud change until the accepted resolution is documented.

If the failure occurred while a desktop prepared the project, examine that desktop's connection separately. The Windows proxy settings reference applies to a Windows preparation workstation, not to Android upload routing. A desktop proxy fix cannot send edits that exist only on the field device.

Step 4: Can the original Android device upload over another path?

Use this branch only when the evidence points to interrupted device-to-cloud transport, with the correct account and permission confirmed. Keep the same device, project, QField version, and pending changes. Record the ordinary authorized connection's result before changing the network, and avoid making new edits during the comparison.

Check the phone has a stable connection and sufficient local storage for its normal workflow. Keep it powered and allow the foreground upload to finish. An upload stopping when the phone sleeps is a different observation from a server refusing the project, so note the circumstances rather than labeling both as an internet outage.

On the Android phone holding the offline work, AethoVPN can provide an alternative outbound route for the same project-change upload. Install the official Android APK, choose a plan that covers the mobile device, select a permitted available location in your country or nearby, and enable global mode. Return to QField and retry the original pending upload without downloading over its local copy.

You can check that phone's browser exit IP and follow the tunnel verification steps as supporting checks. Then inspect whether the cloud accepted the intended change. A tunnel icon, different IP, or successful upload from a desktop is not confirmation that this device's pending edits arrived.

The alternative path does not resolve cloud-worker failures, permission denials, conflicts, schema incompatibility, or missing attachments. Treat the outcome as a diagnosis, not a promise of data recovery. If an interrupted Android upload is the remaining branch, start the three-day Pro trial to compare that transfer; the new-user trial is available once per person.

If the phone already uses a VPN, test an approved ordinary connection with that tunnel disconnected as well. Do not stack consumer and organizational tunnels without the administrator's instructions. Stop if the server has already accepted the changes and now reports an application error; further device route changes target the wrong stage.

Step 5: How do you verify QField project synchronization?

First confirm the relevant changes were accepted, then confirm their application succeeded without unresolved conflicts. Inspect the expected record in the authoritative source or its approved view. Use the same identifier and edited value captured on the original phone; an unrelated record appearing in the project is not enough.

Only after application is verified, obtain a fresh project package on a separate authorized device or in an independent verification copy. Check that the known record contains the expected attributes or geometry. Keep the original edited copy and backup until this comparison is complete; do not use a fresh download to overwrite your only unsynchronized work.

Verify attachments separately when they are part of the task. A feature's attribute appearing does not establish that a photograph or other attachment arrived. Record missing components precisely and let the project owner decide whether the remaining failure is packaging, storage, a path reference, or upload transport.

For support, provide the QField version, operation, sanitized project/change/job identifiers, time, first error, and verification result through an approved private channel. Remove credentials, personal location details, and sensitive field observations from public posts. These checks are a recovery procedure, not a benchmark or a claim that every QFieldCloud deployment behaves identically.

Summary

• Preserve the original field edits and a checked backup before replacing files.
• Separate device upload, cloud application, and download packaging.
• Use job evidence to assign the failure to the right owner.
• Compare routes on the Android device that actually holds the changes.
• Verify an applied record and its attachments in an independent copy.

FAQ

Should I delete the project and download it again?

Not while it contains the only pending edits. Preserve and verify the local backup first, then determine whether the cloud accepted and applied those changes before replacing any working copy.

Can a successful desktop upload prove my phone synchronized?

It cannot prove that edits stored only on the phone were transferred. Use the original field device's changes and a known edited record to verify the actual upload and cloud application.

Is a cloud change entry proof that the source was updated?

It shows that the cloud has a change to handle, not necessarily that application succeeded. Check the change result and corresponding job, then inspect the expected record in the authoritative data. ［3］

Why does the package fail after my changes upload?

Packaging is a cloud stage and can fail while preparing layers or reaching their sources. Inspect that job's error instead of assuming that another mobile VPN location will fix the worker's connection. ［3］

Does this procedure cover directly accessed online layers?

The offline-change recovery steps apply to layers configured for offline editing. Direct access follows a different source path; confirm the layer action and use its owner's backup and editing procedure. ［1］

How should I handle conflicting field edits?

Preserve the evidence and ask the project owner to apply the agreed merge policy. Do not force your version over another user's work or alter the schema merely to make a pending change pass.

When is it safe to retire the old local copy?

After the intended changes are successfully applied and independently checked, including required attachments. Follow the project's retention procedure and keep the verified backup until the owner confirms that the recovery is complete.

Sources

1. QField — QFieldCloud System Documentation
2. QField — My first project
3. QField — Jobs

Sources checked 7 October 2026.