About recoveryCompare recovery

Context Propagation Gap Diagnostic

Check whether tenant, user, workflow, session, retry, parent-call, and spend fields survive each gateway hop.

Analyze gateway context

Trace payload

Paste JSON or NDJSON from an AI gateway, router, or agent trace. Results update live as you type.

Live Preview

Paste a trace payload to see which context fields are present, missing, dropped, or mismatched across hops.

Why this tool

Your gateway logs say tenant=acme, but two hops downstream the agent has no idea who it is acting for. Context Diagnostic walks the trace hop-by-hop and tells you which fields survived, which got dropped, and which were silently rewritten — so you can fix the propagation gap that breaks every downstream attribution report.

How it works

  1. 1

    Capture a multi-hop trace from your gateway → router → agent stack as JSON.

  2. 2

    Paste it above and click Analyze (or load the sample to see the shape).

  3. 3

    Read the field status table and hop progression; the attribution-risk banner summarises the blast radius.

Benefits

Pinpoints the exact hop where a context field disappears.
Surfaces silent rewrites (e.g. tenant_id renamed to tenant) that break dashboards.
Quantifies attribution risk so you can prioritise the fix.
Pure browser parse — no gateway integration, no SDK install.

Frequently asked

Stop re-running this on every incident

Pro saves the diagnostic per service and re-runs it on every deploy.

Save history + team reports → Get Pro

Like what you see? Get early access to the full Auditor

Join the waitlist to save audit sessions and turn trace data into attribution reports.

Join waitlist