Connection Health & Monitoring

Testing a connection

The fastest way to test a connection is to ask an agent to make a live API call using it. Open a new chat session and describe a simple read operation: for example, 'test my Stripe connection by fetching the first customer'. The agent will execute a real API call and return the result or error, confirming whether the connection and credentials are working.

Monitoring via Workflow History

Every automation run is logged in Workflow History with step-level detail. If an API call fails, the log shows the HTTP status code, error message, and the exact step that failed. This is the primary place to diagnose connection issues in production automations.

Signs of a healthy connection

• API steps return 2xx responses with the expected data structures
• MCP tool calls return success: true in their response metadata
• Automations using the connection run without authentication errors across multiple runs

OAuth token health

OAuth tokens expire and can be revoked. Chase Agents auto-refreshes tokens on normal expiry, but if a token is explicitly revoked by the user or the external service, automations will start returning 401 Unauthorized errors. The fix is to go to My Connections and re-authorize the connection.

Rate limits

If your automation makes too many requests to a service in a short time, the service will return 429 Too Many Requests errors. Use wait steps between API calls to respect rate limits, or restructure the automation to batch requests. Check the external service's API documentation for its specific rate limit policy.