Skip to main content
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.

Find the missing step

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. 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.