Troubleshooting Connection Issues

401 Unauthorized

The most common connection failure. It means your credentials are wrong, expired, or have been revoked. For API key connections, verify the key is still valid in the external service's dashboard. For OAuth connections, re-authorize from My Connections.

404 Not Found

The URL or endpoint does not exist. Check that the base URL in your connection matches the service's current API base URL. Check that the endpoint path in your step is correct. API services occasionally change endpoint paths in major version upgrades.

Connection refused or timeout

The service is unreachable. This can happen if the service is down, the base URL has a typo, or Chase Agents's security rules are blocking the URL. Connections to localhost, private IP ranges, and internal domains are blocked by design — those connection attempts will always fail.

Credential variable not resolving

If you see the literal variable name appearing in your requests instead of the actual credential value, the variable name in your step parameter does not match what is stored in the connection. Go to My Connections, open the connection, and verify the exact variable name assigned to each credential. Variable names are case-sensitive.

MCP tool not found

If a use_mcp_tool step fails because the tool cannot be found, the tool_name in the step does not match any tool the server exposes. Use read_resource with type mcp-server and the connection name to see the exact available tools, or call call_mcp_tool with tool_name list_tools on the server to discover available tools.

Getting help

If you cannot resolve a connection issue, share the error from Workflow History in the Chase Agents Discord or email support at charles@chaseagents.com. Include the automation run ID and the failing step's error message.