Troubleshooting
Check the common causes of missing events, source context, and analysis results.
An error does not appear
Confirm init runs before the error and uses the correct node ID, ingest key, and HTTPS base URL.
Check outbound connectivity and the ingest response. For a browser, inspect failed network or CORS requests.
Check sampleRate and beforeSend; an event may be sampled out or filtered.
Enable the SDK debug callback temporarily to inspect delivery errors. Keep diagnostics free of credentials.
For Enterprise, check the https://your-hostname endpoint and its certificate, REELAY_ALLOWED_IPS, the node ID and ingest key, and container-reachable MongoDB connectivity.
Replay or trace context is missing
Replay requires the Browser SDK and replay capture enabled. A backend-only event does not create a browser replay. For linking, confirm the browser request receives trace and session headers, the API permits those headers, and server middleware runs before the route. A configured target list replaces the same-origin default.
Source-aware analysis cannot find the code
Confirm the GitHub App is installed on the selected repository.
Check the node's repository association.
Provide the full deployed commit SHA, not a short SHA or unrelated release label.
Check that the revision is available to the configured GitHub credentials.
A scan fails or returns partial results
Inspect individual stages. Check the scanner configuration, language support, repository size, and build or test commands. For Enterprise agents, scanners are bundled in the image — check the node's dashboard repository link and GitHub App access instead of scanner URLs or keys. Fix the failed stage and rerun; do not treat partial findings as complete coverage.
Enterprise Agent does not connect
Confirm access is active, the runtime token has not been revoked, and the configured control-plane URL is reachable over HTTPS. If pulling the image fails, generate a fresh registry login; it expires after 12 hours and is separate from the runtime token.
Contact support with useful evidence
Include the affected node, environment, timestamp, SDK or agent version, and a sanitized error or run identifier. Describe what you expected and what you observed. Do not send ingest keys, agent tokens, PEM files, or model-provider secrets.