Skip to content
Guide navigation
Troubleshooting

Troubleshoot common results

Use the exact collector result to find the next action without repeating a successful read.

On this page

Read the message first

Message / conditionWhat to checkNext action
Credentials refusedVendor account, password/key, expiry and all supplied sign-insCorrect the vendor credential. Do not replace the ConfigProof token for a device-authentication error.
Not reachableManagement address, VPN, DNS, route and portTest from the collector workstation.
Timed outReachability or slow/throttled APIWait for the current run to settle, then review network/device load.
Not allowedAPI role, scope, trusted source and required read permissionHave the platform owner authorize the missing read.
Not supportedWrong target, unsupported response or installed collector versionUse the matching source and current download.
Read, not deliveredWorkspace token or upload connectivityUse saved-delivery retry after fixing the upload path.
Read and deliveredDelivery result and analysis statusOpen the result; complete any requested selection.

Workspace-token errors

CodeAction
token_missing / token_invalidPaste the complete intended cpc_ token.
token_expired / token_revokedObtain a fresh authorized token.
token_spentA Single use token or its upload allowance is spent; use a new token for additional deliveries.
token_limit_reachedAsk the owner to review unneeded active tokens before creating another.

Certificate or SSH-key change

Verify the device with its owner before updating a changed certificate or SSH key. Check for a wrong hostname, proxy or replaced endpoint; keep global verification enabled.

Some devices or endpoints were not read

Check failed rows and coverage. Manager access does not guarantee managed-device access; cloud reads may depend on roles or licenses. A missing response does not mean empty configuration.

What to include when asking for help

  • Collector version, operating system, vendor and firmware.
  • The selected source and connection method.
  • The exact result message and whether read or delivery failed.
  • A screenshot with names, tokens, addresses and customer labels hidden where sensitive.
  • No passwords, API keys, raw device-state exports or private keys.