Where: UtilityScout, on the phone for sync, then the web Utility Map.
When you finish: the export finishes, or you have stopped a retry loop and sent us what we need.
What you see
A Katapult export stays pending or failed, unsynced or file counts look wrong, or photos and nodes do not appear in Katapult after export.
Files Still Syncing is a hard stop. Do not push to Katapult until field sync is clear. And do not force-export the whole job repeatedly.
Fix it
On UtilityScout, Settings, then Sync Status. Wait until pending uploads clear; Force File Sync if files failed.
On Utility Map, select the job and confirm the export status is not still showing a high unsynced count.
Click Export Data, choose Export to Katapult, confirm, and watch the status on the map overlay or Dashboard Exports.
For a single failed object: select it, History, Exports, Export Data, and try Export Updates first.
Use Force Export All only when updates are not enough and your team accepts that it may create duplicates.
If that did not work
Tell us: the Utility Map job link and object link; a screenshot of the unsynced count or export status; whether you tried Export Updates or Force Export All. Send it from Get help from Cloneable. Escalate when the export stays failed after sync is clear and one careful retry, when unsynced counts keep disagreeing with what fielders see, or when Katapult is missing photos or nodes after a reported success. If exports look stuck across several jobs at once, read When an export does not finish for the broader picture.
Related