Skip to main content

Tool Executions

The Tool Executions page is part of Logs. Open Logs and choose Tool Executions to review actions that agents performed through connected tools.

This view helps identify which agent ran which action, which conversation triggered the action, and whether it completed, failed, or is waiting for approval.

The related Audit Log view in Logs focuses on administrative and system changes. Use Tool Executions when you need to inspect agent/tool activity, tool inputs, tool results, or approval decisions.

This is an administrator and agent-manager workflow. Give access only to people responsible for approvals, troubleshooting, operations, or audit evidence.

Table Overview​

The table contains these columns:

  • Agent - the agent that triggered the action.
  • Conversation - link to the conversation that created the tool execution.
  • Action - function and tool name.
  • Status - current execution or approval status.
  • Resolved at - time when the action was resolved.
  • Resolved by - user who approved or rejected the action.

Above the table, search and pagination help users work with larger numbers of records.

Where the released integration reports it, the execution detail can also expose execution-time information so admins can distinguish a quick failure from a slow or timing-sensitive tool call.

Execution Statuses​

A tool execution can have these statuses:

  • Pending - the action was created and is waiting to run or complete.
  • Success - the action completed successfully.
  • Failed - the action ended with an error.
  • PendingApproval - the action requires human approval before it can continue.

The approval status can be:

  • Approved,
  • Rejected,
  • Pending,
  • Approval not required.

Approval Model​

Approvals are used when a connected function should not run automatically. This is most important for functions that can change business data, send messages, create records, update external systems, or trigger downstream workflows.

Function access is controlled through connection governance:

  • Disabled - the function is not available to agents or workflows.
  • Enabled - the function can run without an approval step.
  • EnabledWithConfirmation - the function can be proposed by an agent, but it must be approved before execution.

When a tool execution is waiting for approval, the table shows the action, conversation, agent, status, and resolution fields. Approving the action allows the tool call to continue. Rejecting the action prevents the tool call from being executed. Both decisions remain traceable through the resolved time and the user who approved or rejected the action.

Use approval requirements for data-modifying functions, high-impact workflow steps, or integrations where a human needs to verify the proposed arguments before the action runs.

Execution Detail​

The execution detail can be opened from the table. The detail shows:

  • arguments passed to the tool,
  • call result,
  • execution time where available,
  • whether approval is required,
  • approval status.

If arguments or results are not available, the detail shows an empty state.

When to Check This Section​

  • When an agent performed an unexpected action.
  • When a user is waiting for a tool result and the action remains Pending.
  • When a tool failed and you need to inspect the input arguments.
  • When the organization uses tool approvals and needs to check who approved or rejected an action.

Debugging Recipe​

  1. Open the related conversation and identify the exact tool action.
  2. Inspect the submitted arguments, result, execution status, and approval status.
  3. Confirm that the selected Connection and connected account have the required upstream permission.
  4. Compare the attempted action with the agent's assigned tools and function governance.
  5. Retry only after correcting the permission, input, Connection, or provider problem.

What Users Should Send an Admin​

Ask users to provide the agent name, conversation title, tool action, approximate execution time, status, error message, and the external record or workspace that should have been used. They must not send access tokens, API keys, passwords, or full secret-bearing screenshots.

  • Use Connections to configure available integrations, function access, and confirmation requirements.
  • Use Audit Log to review administrative changes that affected tools, access, or governance.
  • Use Organization to review tenant-wide security settings that influence public access and safety behavior.
Last updated on