Where: web portal Jobs view and Utility Map, then UtilityScout, on the phone.
When you finish: you know whether the import has brought anything in, whether the poles exist, and why the phone does not show them.
What you see
After a Katapult import the map looks empty, poles or spans are missing, the import seems hung, or UtilityScout does not show the job or its poles.
Fix it
On the Jobs view, find the job and read the Data count column. It shows two dashes until the import brings something in. Large jobs take a while; creating the job only starts the import.
If it stays empty well past a large-job wait, check the message you saw when you created the job (see Create a job), confirm the configuration has an import trigger, and confirm your Katapult key works: your Katapult jobs should load when you choose Add job, then Import from Katapult.
When it succeeds, open View on map. Confirm the organization and team in the header; the wrong team looks like a missing job.
Zoom to the job area (Zoom to Graphics if offered) and check Layers so poles and spans are visible.
Web has poles but the phone does not: in UtilityScout open the Job drop-down and pick the same job name. Stay online long enough for objects to download.
Job selected but the phone map is empty: open Map Layers and clear filters. Map Options is basemap and offline only.
Job list empty on the phone: an Org Admin confirms the job is assigned to the fielder's team.
If that did not work
Tell us: the Utility Map job link; a screenshot of the job's row on Jobs or the empty map; that this was the Katapult path. Send it from Get help from Cloneable. Escalate when the web map has zero objects after a reported success, when the job never appears for a fielder after assignment is confirmed, or when Data count stays empty far beyond a large-job wait.
Related