Troubleshooting

Find what you see in the left column. Every code links to its full explanation in Codes and statuses. A Blocking line always means nothing was written: fix the cause and run the same command again.

An export is refused

You see	Why	Do
PROFILE_UNVERIFIED	The export profile is provisional.	Use a production profile, or add --allow-unverified-profile and tell the recipient (Profiles and authorities).
CRS_GRID_ABSENT	A grid the project’s pipeline needs is not installed, such as the Estonian geoid.	Install it, or add --allow-grid-absent for that pipeline while you wait for it.
CRS_GRID_MISMATCH	An installed grid is not the registered file.	Have the operator install the registered file (Check the coordinate pipelines).
CRS_GRID_HASH_PENDING	A grid is installed but its fingerprint is not recorded.	Have the operator record it with the grid’s installation script.
CRS_PIPELINE_UNKNOWN	The project names a pipeline the registry does not have.	Check --registry and the project’s pipeline.
FROZEN_PACKAGE_CHANGED	You record a package for a freeze instant that already has a different one recorded.	Export and record with a new freeze instant (Record a delivered package).
DXF_EMPTY	Nothing to draw at that freeze instant.	Check the project name and the freeze instant.
DXF_NO_LAYER	A node or span type has no layer in the profile.	Add it in a new profile version.
DXF_LINETYPE_UNDEFINED, DXF_BAD_NAME	The profile has a name or line type DXF does not accept.	Correct the profile (Export profile file).
DXF_BAD_TEXT, DXF_TEXT_TOO_LONG	A label or other text has a line break, a control character, or more than 255 bytes.	Correct the text in the project data.
GPKG_TOOL_MISSING, PDF_TOOL_MISSING	ogr2ogr or typst is not installed.	Have the operator run the installer again.
PDF_TEMPLATE_UNKNOWN	The profile names a book template this version does not have.	Correct the profile, or use the matching ruumica version.
exists and is not an empty directory	The output folder has files in it.	Choose a new folder; an export never overwrites.
--database-url <DATABASE_URL> is required	The database is not set.	Set DATABASE_URL.

A trace cannot be judged, or stays provisional

You see	Why	Do
PROVISIONAL	Only one direction of the fibre is measured.	Measure the other end at the same wavelength and ingest it (Ingest OTDR traces).
SOR_BAD_GROUP_INDEX	The file’s group index is missing or implausible.	Give the data sheet’s value with --ior (Correct the group index).
BIDIR_WAVELENGTH_MISMATCH	The two traces were measured at different wavelengths.	Pair traces of the same wavelength.
BIDIR_LENGTH_MISMATCH	The two traces are of fibres of different lengths.	Check the fibre numbers and cables of both files.
BIDIR_NO_END_EVENT	A trace has no end-of-fibre event.	Set the fibre end in the OTDR software, or measure again.
SLACK_NO_GEOMETRY	The cable’s route has no span lengths.	Record the route first.
SLACK_FACTOR_OUT_OF_RANGE	The fibre is too long or short for its route.	Record the missing slack loop, or correct the route.
FAIL with many unpaired events	Possibly two different fibres of the same cable were paired.	Check the fibre numbers (Check a pair of traces).

A point cloud is refused

You see	Why	Do
LAZ_COUNT_MISMATCH, LAZ_BOUNDS_MISMATCH	The file’s header and its points disagree.	Export the point cloud again from the scanner software.
LAZ_SCALE_TOO_COARSE	Coordinates are stored coarser than 0.001 m.	Export with a scale of 0.001 m or finer.
LAZ_NO_GPS_TIME	The points carry no GPS time.	Export with a point format that includes it.
LAZ_NO_CRS	The file does not say its coordinate system.	Export with the coordinate system written into the file.

Coordinates do not check out

You see	Why	Do
FAIL in asbuilt crs verify	A pipeline does not reach its official test points on this machine.	Do not deliver from it; check grids and PROJ_NETWORK=OFF (Check the coordinate pipelines).
ABSENT or GRID_ABSENT	A grid is not installed.	Install it (Install the Estonian geoid model for Estonia).
Heights look many metres off	They are compared with the wrong kind of height.	Delivered heights are elevations in the national height system, never ellipsoidal heights or depths (Heights and datums).

Field work waits or is refused

You see	Why	Do
PENDING with MISSING_REFERENCE	The change refers to something not received yet.	Usually nothing: let the other device sync.
PENDING with a hold reason	The server holds the change, for example for a missing height.	See the hold reasons.
CONFLICT	The change contradicts another one; its data is kept.	The office decides (Offline sync).
REJECTED	Refused for good; the reason says why.	See the rejection reasons.
Work waits for days	Something needs a person.	Run asbuilt sync pending (Watch for waiting work).