Troubleshooting

Symptom: tool never reaches downstream

• Verify the tool is mapped on the upstream connector and included in the host configuration.
• Check credits / plan gating in Agentsyx (upstream may block before forward).

Symptom: authentication errors

• Distinguish host ↔ Agentsyx OAuth issues from Agentsyx ↔ downstream credential issues (API keys, mTLS, etc.).

Symptom: unexpected arguments

• Models may omit optional fields; validate and default in the downstream server.
• Compare against Injected parameters & metadata once documented from code.

What to capture for support

• Timestamp, upstream deployment, tool name, correlation / request id (if present), redacted user id, and downstream server version.

For platform-specific HTTP status meanings (e.g. 401 vs 402), align wording with apps/saas-starter after reviewing the proxy implementation.