# Troubleshooting

Resolve connection, provider, watch and data-source failures without hiding missing evidence or repeating paid requests.

## My AI cannot see the tools

Confirm that the client supports remote Streamable HTTP MCP and that its plan/admin settings allow custom connections. Use the exact /mcp URL, complete OAuth or configure a Bearer header, and reconnect if the grant expired. Call network_status to confirm execution, not just registration.



## Research asks for a key

Open Setup → Optional data and save the requested provider credential. Keys do not go in chat. A saved key may lack endpoint permissions or credit. Check the provider console and supported Robinhood methods when a read fails. Ultron does not substitute a different chain.



## A paid request says unknown

The service could not confirm the upstream outcome. It may already have incurred a charge or started an actor. Check the provider console before creating another request. Ultron deliberately does not repeat an uncertain paid action automatically.



## A watch stopped producing observations

Check the watch's last error, exact asset identities and source timestamps. Missing metrics, stale/unknown transport age or changed pool assets fail the observation. A threshold that stays true does not repeatedly alert; it rearms only after becoming false.



## Messaging — Coming soon

Connect Ultron to your existing AI through MCP. Approved watch conditions create events in your AI through scheduled checks. Telegram and Discord are coming soon.



## Two prices do not agree

Check token identity, quote asset, raw units, issuer multipliers and observation times first. A stock reference quote and an indexed pool price measure different things. Do not discard a disagreement or call it executable arbitrage without checking the surrounding mechanics.