Skip to main content
Errors from trace session capture and delivery. Run atlanai trace integration doctor first. It reports hook registration state, daemon reachability, and endpoint connectivity in one command.

​
Session does not appear in trace session list after completion

The session was not recorded locally after it finished.

​
Cause

The integration hook was not registered before the session started, or the daemon was not running during the session. Sessions are captured only when the hook is active at session start.

​
Solution

Verify hook and daemon state before starting a new session.
  1. Run atlanai trace integration doctor to confirm the hook is registered and the daemon is running.
  2. Confirm the daemon can reach the configured endpoint.
  3. Start a new session after the doctor check passes.

​
Outbox shows sessions queued but delivery does not progress

Sessions are captured locally but are not being exported to the Registry.

​
Cause

The daemon cannot reach the Registry endpoint. Sessions queue in the outbox until a successful delivery connection is established.

​
Solution

Diagnose the connectivity issue before retrying delivery.
  1. Run atlanai trace integration doctor to identify the connectivity issue.
  2. Resolve the reported issue.
  3. Run atlanai trace reconcile to trigger an immediate delivery retry.

​
requeue-dlq does not clear the dead-letter queue

Items moved back to the outbox continue to fail.

​
Cause

The underlying delivery error is still present. Re-queuing before resolving the root cause moves items back to the outbox, where they fail again and return to the dead-letter queue.

​
Solution

Resolve the root cause before re-queuing.
  1. Run atlanai trace integration doctor to identify the delivery issue.
  2. Run atlanai auth status to confirm the credential is valid.
  3. Resolve all reported issues.
  4. Requeue with atlanai trace outbox requeue-dlq after both checks pass.

​
See also

  • Capture traces: Install integrations and inspect local trace capture and delivery.
  • Run diagnostics: Inspect daemon logs, runtime state, and support bundles.

​
Need help

If you need assistance after trying these steps, contact Atlan support.