Sync problems¶
QFieldCloud projects aren't listed¶
What you see: Empty list, or QFieldCloud projects could not be listed.
What to check:
- Test the saved Source
- Server URL ends like
https://app.qfield.cloud/api/v1/ - Username and password
- QFieldCloud sync is enabled on this GeoJibe server
- The host has
qfieldcloud-cliinstalled (administrator)
Mergin Maps projects aren't listed¶
Listing only includes projects you created or that were shared with you. Check the URL (https://app.merginmaps.com/ is the default) and that Mergin Maps sync is enabled.
This project has no GeoPackage¶
A Sync Job needs one .gpkg in the project. Add one in QField / Mergin Maps, then inspect the project again.
My Sync Job says "No changes"¶
What you see: Succeeded — No changes
Why it usually happens: GeoJibe compared the remote project to the last successful sync and found no change.
What to check: Confirm new features were uploaded to QFieldCloud or Mergin Maps. Then Run Now.
This status is normal. It is not a failure.
Two-way Mergin Maps Jobs do not use “No changes”. They report Initialized or Synchronized.
QFieldCloud and Mergin Maps cannot be used as Convert Job Sources¶
What you see: That error when you try to Convert or inspect them as a dataset.
Use a Sync Job instead. See Sync QFieldCloud with PostGIS.
Sync Jobs can only deliver to PostGIS¶
Sync writes a GeoPackage into a PostGIS schema. There is no table name or write mode. Download, S3, and GeoServer are not Sync Destinations.
Synchronization runtime is unavailable¶
The GeoJibe host is missing QFieldCloud CLI, GeoDiff, or Mergin Maps tools. This is an installation issue. See Installation.
Reset did not empty PostGIS¶
Reset synchronization state only clears GeoJibe's local sync files. It never drops the schema.
To rebuild destination data, use Reinitialize destination schema and type the schema name to confirm. For two-way Mergin Maps this also replaces {schema}_base.
This Job is already running¶
Wait for the current cycle. Interval schedules skip overlapping ticks.