Skip to main content
Debug Mode allows developers and operators to monitor the internal bot execution process in real time directly from the platform interface. While the assistant processes user requests, logs are streamed into the Live Debug Feed, showing step-by-step execution details including tool calls, actions, execution time, responses, warnings, and errors.
Debug Mode

Enabling Debug Mode

Debug Mode can be enabled directly from the bot Flow editor. Navigate to:
Enable the Debug mode checkbox in the top-right corner of the Flow editor interface.
Debug logs will start appearing in the Live Debug Feed only after Debug Mode is enabled.

What is Debug Mode

Debug Mode is a real-time debugging interface that helps monitor:
  • Active flows
  • Tool execution
  • Action execution
  • LLM requests and responses
  • Errors and warnings
  • Custom logs from Function actions
  • Execution timing and performance
Logs are streamed directly from the backend and displayed live without refreshing the page.

Why Use Debug Mode

Live Debug Feed

The Live Debug Feed displays all interaction logs in chronological order. Each log entry contains: Clicking a log entry opens additional details including full JSON payloads, arguments, and execution results.

Session Start Example

Shows the interaction start and currently active flow.

User Request Example

Shows the incoming user request and available tools provided to the model.

Tool Execution Example

Displays:
  • Tool name
  • Arguments passed by the LLM
  • Tool description
  • Tool execution start

Action Execution Example

Each action execution contains:

Tool Completion Example

Shows total execution time for the entire tool execution chain.

Bot Response Example

Displays:
  • Final assistant response
  • Total generation time
  • API provider version
  • Model name

Custom Logs in Function Actions

Function actions can send custom logs directly into Debug Mode using interaction["_LOGGING"].

Example

These logs appear together with system logs inside Live Debug Feed.

Logging Levels

Full Debug Flow Example

Technical Details

  • Logs are streamed through Redis pub/sub.
  • Events are stored in events:{interaction_uuid} queue with TTL.
  • Each log contains:
    • id
    • timestamp
    • level
    • message
    • optional details
    • optional nested children
  • Nested logs are displayed in UI as expandable trees.
  • Logs remain available during TTL lifetime after interaction completion.

Notes

  • Debug Mode is intended for development and troubleshooting.
  • Full responses and action results may contain sensitive information.
  • Excessive debug logging may affect readability during large interactions.
  • Custom Function logs are supported only inside Function-type actions.