Review Tool Executions
Tool executions show what an agent or workflow did through a connected service. Review them when you need to understand an output, investigate a failure, approve an action, or confirm that an external system was changed.
What to Look For
- Which tool was used.
- Which connection was used.
- Whether the action succeeded or failed.
- What inputs were sent.
- What result came back.
Table and Statuses
The Tool Executions table shows Agent, Conversation, Action, Status, Resolved at, and Resolved by.
Execution statuses include Pending, Success, Failed, Waiting for approval, and Unknown. Approval statuses include Approved, Rejected, Pending, and Approval not required.
Open the detail from the Status column to inspect arguments, result, approval requirement, and approval status.
Approval is evaluated on the specific function that was called, not only on the connection as a whole. For example, a Google Drive connection may allow read functions without approval while file updates or deletes require approval. If an execution says Approval not required, it usually means the admin configured that function as safe for direct use.
First Status Map
For everyday review, group tool executions into four practical outcomes:
| Outcome | What it means | What to do |
|---|---|---|
| Ran successfully | The tool completed. | Verify the result if it affects a customer, ticket, file, calendar, or CRM record. |
| Waiting for approval | The tool is paused before a sensitive action. | Review the intended action and ask the approver to approve or reject it. |
| Failed | The tool could not complete. | Check the error, connection, and permissions, then share details with an admin if needed. |
| Changed another system | The tool wrote to an external system or file. | Confirm the target record, message, event, or file in that system. |
Detailed arguments, response payloads, retry behavior, and audit investigation are mainly for debugging. Start with the outcome first, then open the detail only when the result is unclear or risky.
When to Review
Review tool executions after important write actions, failed workflows, unexpected answers, or permission errors. If the tool changed an external system, also verify the result in that system.
If an execution failed because of access, expired credentials, or missing permissions, ask your administrator to review the connection.
Debugging Recipes
A Tool Is Waiting For Approval
- Open Tool Executions.
- Find the execution with Waiting for approval.
- Open the detail from the Status column.
- Review the arguments and intended result.
- Ask the approver to approve or reject it.
A Tool Failed
- Open the failed execution.
- Check the arguments sent to the tool.
- Check whether the connection is personal or shared.
- Verify the same action in the target system if possible.
- Share the action name, agent, conversation, error, and connection name with your admin.
An External Record Was Changed
Use Resolved at and Resolved by to understand when and by whom the action was approved or completed. Then verify the record in the target system, such as Jira, HubSpot, Slack, Google Calendar, Gmail, or Drive.