Troubleshooting

Diagnose device presence, local scope, approvals and uncertain execution without weakening access.

Device is offline

Check whether the service is running and can reach the configured HTTPS origin. A sleeping laptop is expected to be offline; it reconnects and polls immediately after waking.

adc-node status
adc-node logs
adc-node restart

No folders are visible

Confirm the local access mode first. Then compare exposed folders with the device policy and the Agent authorization; every layer can narrow the previous one.

adc-node status
adc-node roots list
adc-node roots add "/path/to/workspace" --label Workspace

Approval is waiting

Open Approvals before the invocation expires. Confirm the Agent, device, tool and path. A changed, deleted or revoked authorization cannot be approved.

adc approval list --json
adc approval approve APPROVAL_ID --json

Unknown outcome

The side effect may have happened, but a terminal receipt cannot be proven. Inspect Activity and the target resource; retry only with the original idempotency key after reconciliation.

adc audit show INVOCATION_ID --json
adc task result JOB_ID --json

Tool is denied

Read the returned reason before broadening access. Check the Agent tool list, device execution switch, writable-folder policy and Connector access mode.

adc access show ACCESS --json
adc device show DEVICE --json

Collect evidence before changing policy

The exact error code and retryable value.
Invocation ID, job ID and approximate timestamp.
Connector status and relevant structured log lines.
Current device and Agent authorization summaries without credentials or file content.

Do not paste access keys, session cookies, device private keys, file content or production URLs into a public issue.