tickwire_no_reply

The MCP tool sent the request but got no reply. If it was a trade, it may have executed.

MCP tool result. Unknown: it may have executed. Resolve it with the same idempotency key before acting.

Likely cause: The connection dropped or timed out after the request was sent.

What to do: For a trade, call get_trade_status with the same idempotency_key before doing anything else. Reads can be repeated.

Retry: Only with the same Idempotency-Key (or clientId). The first attempt may have executed; never resend a trade blindly.

Listed under Outages and timeouts in Errors. Send the error’s requestId to support and we can find the request.