Skip to content
Karyam

AI Flow Logs

AI flow Logs provide complete visibility into how an AI Flow executes.

Every flow execution generates a sequence of structured events that allow teams to understand:

  • Which step is currently running
  • Which tools were executed
  • Whether approvals were requested
  • Why execution paused
  • When execution resumed
  • Why a AI flow failed

This makes AI flows observable, debuggable, and auditable.


A typical execution may look like this:

REQUEST
↓
TOOL_EXECUTION_START
↓
TOOL_EXECUTION_END
↓
STEP_FINISH
↓
APPROVAL
↓
PAUSED
↓
RESUME
↓
RESPONSE

AI flow Logs provide complete visibility into how an AI Flow executes.

Every flow execution generates a sequence of structured events that allow teams to understand:

  • Which step is currently running
  • Which tools were executed
  • Whether approvals were requested
  • Why execution paused
  • When execution resumed
  • Why a AI flow failed

AI flow Logs can be accessed from:

OPERATE
└── Runs
└── Logs

This makes AI flows observable, debuggable, and auditable.


Indicates the beginning of a AI flow execution.

Example:

REQUEST
Flow: VPN Access Restoration
Run ID: flow_01HABC123
Status: RUNNING

Generated when a AI flow step starts executing a tool.

Examples include:

  • PostgreSQL Queries
  • Email Notifications
  • Webhooks
  • MCP Tools
  • Vector Search

Example:

TOOL_EXECUTION_START
Tool: PostgreSQL
Operation: Employee Lookup
Status: EXECUTING

Generated when tool execution completes.

Example:

TOOL_EXECUTION_END
Tool: PostgreSQL
Duration: 245ms
Status: SUCCESS

Generated when a AI flow step completes.

Example:

STEP_FINISH
Step: Verify Employee Eligibility
Status: SUCCESS

Generated when a connected integration requires authentication before execution can continue.

Example:

AUTH_REQUIRED
Integration: GitHub MCP
Reason: OAuth token expired
Status: WAITING

Generated when a AI flow requests human approval.

Example:

APPROVAL
Approval Type: Manager Approval
Requested For: VPN Restoration
Status: REQUESTED

Generated when AI flow execution pauses while waiting for approval.

Example:

PAUSED
Reason: Waiting for manager approval
Status: WAITING_APPROVAL

Generated when AI flow execution resumes after approval.

Example:

RESUME
Approved By: John Doe
Status: RESUMED

Approvals may result in:

APPROVED
REJECTED

Example:

APPROVAL
Status: APPROVED

or

APPROVAL
Status: REJECTED

Each AI flow execution maintains a current status.

Status Description
INFO Informational event
SUCCESS Operation completed successfully
FAILED Execution failed
REQUESTED Action has been requested
EXECUTING Currently executing
RUNNING AI flow is active
WARNING Non-blocking issue detected
WAITING Waiting for external input
TRANSFERRED Execution transferred
CANCELLED AI flow cancelled
WAITING_APPROVAL Waiting for human approval

Status Description
APPROVED Request approved
REJECTED Request rejected
RESUMED AI flow resumed
PAUSED AI flow paused

10:01:02 REQUEST
10:01:03 TOOL_EXECUTION_START
Employee Lookup
10:01:03 TOOL_EXECUTION_END
SUCCESS
10:01:04 STEP_FINISH
Employee Verification
10:01:05 APPROVAL
Manager Approval Requested
10:01:05 PAUSED
Waiting for Approval
10:03:20 RESUME
Manager Approved Request
10:03:21 TOOL_EXECUTION_START
Create Ticket
10:03:22 TOOL_EXECUTION_END
SUCCESS
10:03:23 RESPONSE
10:03:24 STEP_FINISH
10:03:25 SUCCESS

Employee Request
↓
REQUEST
↓
Verify Employee Status
↓
TOOL_EXECUTION_START
↓
TOOL_EXECUTION_END
↓
APPROVAL
↓
PAUSED
↓
RESUME
↓
Create IT Ticket
↓
RESPONSE

AI flow Logs provide:

  • Execution visibility
  • Approval tracking
  • Operational debugging
  • Compliance auditing
  • Production observability

This allows organizations to operate AI AI flows with confidence.


AI flow Logs work alongside:

  • Agent Logs
  • RAG Logs
  • Execution Traces
  • Token Usage
  • Cost Analytics

Together they provide complete visibility into production AI systems.


Continue with:

  • RAG Logs
  • Execution Traces
  • Token Usage
  • Cost Analytics
  • Debugging