RESOURCES · DOCS · AGENT STUDIO · HELP

Troubleshooting

Connection failures, malformed manifests, Python sidecar issues, OTLP errors, and replay nondeterminism.

HELP
Agent Studio Open
LOCAL-FIRST
ConnectComposeTracesReplayObserveShip
COMPOSE · TOOL CALL
{ "tool": "refund_order", "order_id": "ORD-1042", "dry_run": true }
TOOLS
18
TRACE
.ast
P95
812ms
TRACE READOUT
SECTION
Help

Where this entry sits in the docs index.

READ TIME
10 min

Pace it for a coffee or a coffee break.

SECTIONS
1

Each one stands alone and is copy-paste safe.

INSTRUMENT READOUT · HELP
THE WALKTHROUGH

What you will actually do.

STEP 01
HELP

Fast checks

Most failures are caused by a server process that exits early, missing environment variables, malformed JSON-RPC responses, blocked remote headers, or provider-key configuration.

01

Connection failed: retry with server logs visible and verify cwd/env.

↳ CHECK
02

Tool call failed: copy the raw JSON-RPC request and validate schema fields.

↳ CHECK
03

Model API failed: open Settings, Models and run provider smoke check.

↳ CHECK
04

Replay nondeterminism: lock mocked tool outputs and provider model version.

↳ CHECK
05

OTLP malformed: confirm JSON vs proto endpoint and content type.

↳ CHECK
06

SQLite write failed: check disk space and trace-store location permissions.

↳ CHECK
07

Python sidecar unhealthy: rebuild the venv from Settings, Advanced.

↳ CHECK
HELP

Next time, it's already a replay.

The path you just read becomes the path you can repeat. One trace, one artifact, one gate the next release has to clear.

Troubleshooting | Agent Studio Open Docs