> ## Documentation Index
> Fetch the complete documentation index at: https://docs.impact.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot JavaScript capture

> Use runtime diagnostics to repair startup, partial capture, OTLP delivery, and missing Traces.

Start with `runtime.status()`. It identifies the loaded artifact, integration owners, activation, capture limits,
delivery and cleanup. Match the exact native operation, installed versions and route in the
[integration catalogue](https://docs.impact.ai/sdk/javascript/integrations.md).

## Find the missing step

| Observation | What to check |
| - | - |
| Startup reports `unavailable` | Resolve the diagnosis for the discovery endpoint and key. After a settled failure, call `init()` explicitly and retain the new handle. |
| No native work appears | Initialize before the application constructs its client, or follow the integration's native setup. Check for disabled owners, unsupported peers, or a route that your customer provider owns. |
| A captured field is missing | Check the local policy, native client settings, delivery of content logs, operation/helper limits, and whether the caller actually consumed the native output. Review partial and omission markers. |
| The receiver rejects records | Check `runtime.status().diagnosis` for authorization, an unrecognized OTLP route, or a rejected request. After changing an active runtime's endpoint or credential, restart or redeploy. |
| Export finishes but the Trace is missing | Open the intended Impact Product and Environment. Compare the recent service, operation and runtime ID to the same execution. Check both trace and log outcomes locally. |

Repeat the same type of operation with a fresh Interaction ID after repair. Keep a single owner for each native
boundary. A second owner can duplicate capture. A successful later export clears the current failure hint while
cumulative counters retain earlier delivery loss.

Run one representative application operation, then flush or shut down and inspect its Trace and Recorded fields
in Impact. Check the input, output, model, usage and real tool effects available to that operation. A setup report
can show a running SDK awaiting traffic or a local delivery problem. Use the actual Trace to establish readable
Product evidence. Keep the route and Environment revisions current when using a supplied setup report.

## Install alongside existing telemetry

npm 11.17.0 can reject incremental installation into an existing OpenTelemetry 3 app when resolving an absent
optional Google ADK peer. Use `npx --yes npm@11.21.2 install impact-ai@0.4.0-rc.10` to select the documented
installer. Preserve the existing native client pins and lockfile.

## Read delivery results

The managed trace and log routes use OpenTelemetry protobuf codecs and an Impact-owned HTTP transport.
Each physical batch makes at most three attempts within a 30-second deadline for connection failures and HTTP
429, 502, 503 or 504, honoring bounded `Retry-After`. HTTP 408 and 500, other nonretryable rejection and successful HTTP
acknowledgements, including partial rejection, are never retried. Local counters distinguish accepted, rejected and
unknown records. A warning-only acknowledgement reports a safe warning without copying receiver text.

## Get setup help

Contact Impact AI at [biz@impact.ai](mailto:biz@impact.ai). Include your SDK and Node versions, integration
and operation, local diagnosis code, and a content-free description of where the Trace stopped. Keep keys,
prompts, and raw telemetry out of the message.

## Report a security issue

Use the [private security reporting process](https://docs.impact.ai/security.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.