Login
Updated on June 10, 2026

Runtime Configuration

Estimated reading: 7 minutes

The Runtime Configuration settings allow users to control workflow execution, monitor performance, and manage execution behavior across development, testing, troubleshooting, and production environments.

By fine-tuning these settings, users gain better visibility into workflow execution, enable targeted monitoring, and improve system reliability and fault tolerance.

Runtime Configuration helps balance:
 a. Real-time visibility into workflow execution
 b. Post execution analysis for debugging and auditing
 c. Execution reliability through intelligent failure handling

Key Benefits

Runtime Configuration enables users to:
1.Improve debugging with better visibility into workflow behavior
2.Enhance reliability through effective failure handling mechanisms
3.Support auditing and compliance with execution tracking
4.Adapt monitoring based on development, testing, or production needs

The Runtime Configuration section contains the following options:

1. Activity Tray 
2. Surround With AI (Upcoming)
3. Execution Trail

1. Activity Tray

The Activity Tray provides real-time visibility into workflow execution. As a workflow runs, users can observe each step as it executes without waiting for logs or final outputs. This makes it easier to identify delays, detect unexpected behavior, and diagnose performance bottlenecks during both development and troubleshooting.

When Activity Tray is enabled and a workflow starts executing, the Runtime Monitor dialog is automatically displayed, providing detailed visibility into workflow execution and runtime behavior.

Core Features

1. Displays currently executing activities in real time.
2. Tracks workflow progress step by step.
3. Simplifies debugging during development.
4. Improves visibility into long-running workflow executions.

Runtime Monitor

The Runtime Monitor, accessible from the Activity Tray, provides real-time visibility and control over workflow execution. It enables users to monitor, analyze, and manage bot activity as it runs, eliminating the need to wait for execution to complete before reviewing logs.

This capability allows issues to be identified and addressed immediately, improving both development efficiency and production reliability. It is particularly useful for debugging, monitoring live workflows, and optimizing performance.

How It Helps

a. Detect issues early by identifying failures, warnings, or unexpected behavior during execution.
b. Understand workflow behavior through live activity progression.
c. Identify performance bottlenecks, retries, or inefficient workflow steps.
d. Take immediate action by stopping workflow execution when necessary

Execution Details

The Execution Details section provides multiple views of a running workflow, enabling users to analyze execution from different perspectives.

1. Execution Order

Displays the sequence in which activities are executed within the workflow, helping users understand workflow progression, execution flow, and dependencies in real time.

2. Logs / Output

Provides detailed runtime logs, including messages, warnings, errors, and outputs generated during execution. This information helps users identify and troubleshoot issues effectively.

3. Stats

Displays performance-related metrics, such as execution duration, delays, retry counts, and failures, allowing users to evaluate overall workflow performance.

4. Health

Shows the operational status of the workflow through health indicators and activity-level insights, helping users quickly identify irregularities or performance issues.

Stop Control

The Stop action allows users to immediately terminate a running workflow. This is useful when:

   a. The workflow is stuck in a loop or an unexpected state.
   b. An error may impact downstream systems.
   c. Immediate intervention is required to prevent incorrect execution.

Stopping the workflow from the Runtime Monitor also stops it in the Designer, ensuring consistency across the platform.

Minimize vs. Close

Understanding the difference between minimizing and closing the Runtime Monitor helps preserve active monitoring sessions:

a. Minimize: Hides the Runtime Monitor without interrupting workflow execution. Users can reopen it from the system tray (Hidden Icons panel) and continue monitoring the same session.

b. Close: Ends the current monitoring session. To resume monitoring, the workflow must be restarted, which creates a new session.

2. Surround With AI (Upcoming)

Surround With AI is an upcoming feature designed to simplify exception handling and retry management during workflow design. It automatically generates AI-assisted retry and recovery patterns, reducing the need for manual error-handling configurations and helping users build more resilient workflows.

By intelligently applying fault-tolerance strategies, Surround with AI enables users to design workflows that can handle failures more effectively while minimizing development effort.

Core Features

1. Automatically generates AI-assisted retry and recovery patterns.
2. Simplifies exception handling during workflow design.
3. Reduces the need for manual error-handling configurations.
4. Enhances workflow resilience through intelligent fault-tolerance strategies

3. Execution Trail

The Execution Trail captures the complete end-to-end execution path of a workflow, including branching decisions and execution insights. It serves as a powerful mechanism for post-execution analysis, enabling effective debugging, auditability, and root-cause investigation.

It records the detailed, step-by-step flow of a workflow after execution and provides a comprehensive view of workflow behavior, helping users validate outcomes and perform in-depth execution analysis.

Visual Indicators

a. Successful activities are highlighted in green.
b. Failed activities are highlighted in red.

Core Features

1. Captures the complete workflow execution path from start to finish.
2. Records branching decisions and activity-level execution details.
3. Provides visual indicators for successful and failed activities.
4. Supports auditing, validation, and root-cause analysis of workflow executions.

Default Behavior

By default, Activity Tray, Execution Trail, and related monitoring features are disabled to minimize performance overhead during workflow execution.

Users can enable these features in either of the following ways:
    a. From the Runtime Configuration page by enabling the required options.
    b. During workflow execution, through a popup that appears when starting a workflow, allowing users to enable the desired monitoring features. Once enabled, these features remain active for subsequent workflow executions until they are manually disabled.
This flexible approach allows users to activate advanced monitoring capabilities only when needed, such as during debugging, troubleshooting, or execution analysis, while keeping routine workflow executions lightweight and efficient.

Configuration - Previous Activity Configuration
Share this Doc

Runtime Configuration

Or copy link

CONTENTS

Powered By Sutherland

Robility Chatbot
Robility Assistant
Online