Review executions and diagnose errors
Use history to understand successful calls, failures, and response times.
Updated August 3, 2026 · 9 minReview history
Executions contains manual tests and agent calls. Each row shows status, request, origin, date, duration, and a result or error summary. Use origin and agent ID to locate related configuration and conversations.
Diagnose by error type
- 401 or 403: missing, expired, or unauthorized credential.
- 404: incorrect URL or resource.
- 400 or 422: invalid parameters, body, or collected data.
- 429: external service limit.
- 5xx: temporary or internal provider failure.
- Timeout: slow or unreachable endpoint, or excessive synchronous work.
Correct and save configuration, repeat a manual test, then validate from a conversation.
Handle history carefully
Deleting an obsolete execution hides it from Studio; it is not a substitute for external audit policies.
When contacting support, share the date, tool type, status, and error message—never passwords or tokens.