The target does not appear
Confirm organization access, an active API key, administrator permissions, and outbound connectivity to the installation and API endpoints. Review the agent service logs for the relevant failure. Use the authenticated Console install command from the installation guide.
A target appears but has little evidence
Enrollment confirms the target identity; it does not confirm complete workload coverage. Check Scan Runs, collection status, timing, and whether the workload exercised the relevant process and traffic paths.
An expected path is missing
Review the collection window and available observations. Repeat collection under representative workload conditions when appropriate. An absent observation is not proof that the activity cannot occur.
The existing identity needs recovery
Keep the stable identity at /var/lib/laviq/agent-id. Do not create a new UUID just to retry enrollment. When the existing identity is known from the platform, the documented recovery command is:
sudo laviq agent-id restore --uuid <EXISTING_UUID_FROM_PLATFORM>Contact Laviq when the identity is unknown or the recovery path is unclear.
Ask for help
Include the target identifier, approximate collection time, scan status, and a description of the issue. Exclude API keys, private-key material, and sensitive workload data from a public enquiry. Use Laviq support to discuss the next step.