Get started →

OBSERVE · PRESERVE · CONTROL

Documentation

Guides, reference material, and technical information.

Troubleshooting

Resolve incomplete evidence without hiding the failure.

An attempt has no completion

Treat the result as unknown. Correlate the target, queue identity and attempt ID, and check for a terminal outcome. A start record or baseline-loaded record alone does not establish successful verification.

Import is rejected

Use UTF-8 JSON Lines without a BOM and retain the leading queue or receiver_stream header. Imports are limited to 2 MiB and 1,000 events. Conflicting sequence records reject the entire submission; correct the source export rather than deleting evidence.

No records appear

Check the chosen target and filters. Observation and scan-health views are distinct. Registering a target alone does not create evidence or start collection.

An artifact cannot be downloaded

Only published releases expose artifacts. Downloads validate stored bytes against their digest. Ask the release administrator to investigate a missing or changed artifact.

Your changes were not saved

If another operator updated the same inventory record, reload it and reconcile the newer values. Do not blindly resubmit stale edits.

Need more help?Find guidance, platform details, and troubleshooting.
HEXROOK | PRIVACY · CONTROL · FREEDOMINDEPENDENT TOOLS FOR A MORE SECURE WORLD.