Use the section that matches what you can see. These are safe first checks, not a claim that every problem has the same cause.

That is correct and nothing is lost.

A counter reading zero of seven means there are seven objects here and none of them are measured yet. It counts measurements, not the objects you placed.

If you have placed poles rather than measured them, zero is the right number.

A blocked camera permission is one possible cause. When you are adding a photo to a field, the app tells you directly, with a message and a button that opens Settings for you. The high-accuracy measurement camera does not explain it the same way, it just stays black. If you do not see a message, check the permission yourself before assuming the camera has failed.

If the camera is allowed and still black, close the app fully and reopen it before reporting it.

Do not sign out and do not delete the app. Your work is on the phone until it sends, and both of those risk it. Signing out is the one action that can lose a day.

Your Settings screen can also help here. Tap Person Icon → Settings to see your un-synced file count and a Force File Sync button that pushes everything again. If any files have failed, a Retry Failed Syncs button shows there too, and using it never deletes anything. The pill on the map is still the quickest check while you are working.

There are two controls that look like they confirm, and only one of them saves: the one inside the slide-up editor. The outer card's confirm closes the panel and discards the edits.

If you tapped the outer one, reopen the guy, re-enter the values, and save from inside the editor. More detail.

This is a configuration gap, not something to fix from the field. Your organization's backend configuration is missing a line template for the connection type you are drawing.

Tell your Admin which connection type triggered it. They add the missing template in the web configuration manager. More detail.

AR measurement can take a while to start when the phone's processor is under heavy thermal or compute load. You may see a message that processors are behind. You may see no message, only a wait.

This is expected when the phone is running hot or busy. It is not a broken app.

Do not sign out. Do not delete the app. Your work is on the phone until it sends.

Then report it with what you saw on screen, using the list below.

Have these ready so we can investigate the problem without another round of questions:

Do not bother reading off the version number. It does not reliably say which build you are on, so it will not help. Instead, tap Person Icon → Settings → Upload Diagnostic Data before you report it. That uploads a copy of everything the app has stored on your phone, including your local job data and any photos still waiting to sync, labeled with your name and email so engineers can find it. It is far more accurate than the version number.

The ? on the map opens those tutorial videos and Chat. Try them before you get out of the truck.

If something is wrong, do not sign out and do not reinstall while work is unsent. Protect the data on the phone first, then troubleshoot.

Start ready, complete the record, finish synced. For sign-out, device, and measurement options, use Your app settings as a reference rather than first-shift reading.