Running Workflows

Learn how to save and run designed pipelines, and explore monitoring features.

Save

You must save changes before running. Click the Save button in the top toolbar or use the shortcut Ctrl+S.

Validation

Basic connection status and missing required settings are validated when saving. If there are errors, saving is blocked and problematic nodes are highlighted.

Manual Run

To run the pipeline immediately:

1. Click the Run button (play icon) in the top toolbar.
2. When execution starts, the button changes to Stop, and the connection lines on the canvas animate to show the flow.
3. To stop execution, click the Stop button.

Scheduling

To run the pipeline periodically:

1. Click Settings (gear icon) in the top toolbar.
2. Set the frequency in the Schedule tab.
3. After saving the settings, the status bar displays Scheduled status.

Schedule Options

Option	Description	Example
Interval	Run at fixed intervals	Every 1 hour, every 30 minutes
Daily	Run at a specific time daily	Every day at 9 AM
Weekly	Run at specific day/time weekly	Every Monday at 6 AM
Cron	Cron expression	0 9 * * 1-5 (9 AM on weekdays)

Cron Expression Examples

# Min Hour Day Month Weekday
  0   9    *   *     *     # Every day at 9 AM
  0   */2  *   *     *     # Every 2 hours
  30  8    *   *     1-5   # 8:30 AM on weekdays
  0   0    1   *     *     # Midnight on the 1st of every month

Monitoring

[Screenshot] Workflow Execution Monitoring

Real-time Status

During execution, each node's status is displayed with colored borders.

Status	Color	Description
Running	Blue (animated)	Currently running
Success	Green	Completed successfully
Failed	Red	Execution failed
Pending	Gray	Waiting (waiting for dependency nodes to complete)
Skipped	Yellow	Skipped (condition not met)

Run History

View recent execution results at a glance through the Run History Bar in the top toolbar.

• Each bar represents an individual execution.
• Colors distinguish success (green) from failure (red).
• Click a bar to view detailed information about that execution.

Batch Details

Clicking an execution shows the following information:

• Start/End Time: Execution duration
• Per-Node Status: Execution results for each node
• Records Processed: Input/output data statistics
• Logs: Detailed execution logs

Error Handling

What to Check When Execution Fails

1. Click the Red Node: Select the failed node.
2. Inspector Panel: Check the error message and stack trace.
3. Logs Tab: Review detailed execution logs.

Common Error Types

Error Type	Cause	Solution
Connection Error	Data source connection failed	Check network, authentication credentials
Schema Mismatch	Schema inconsistency	Verify input/output schema mapping
Code Error	Python/SQL code error	Fix code syntax, logic
Resource Limit	Insufficient resources	Reduce data size, adjust partitions
Timeout	Execution time exceeded	Optimize query, adjust timeout settings

Retry Settings

You can configure automatic retries on failure in the pipeline settings:

• Retry Count: Maximum number of retries (default: 0)
• Retry Interval: Wait time between retries
• Retry Condition: Retry only on specific error types

Runtime Environment Settings

Container Image

You can specify the Docker image to use for pipeline execution.

1. Open Settings → Runtime tab.
2. Enter the image name in the Image field.
3. Set Resource Limits (CPU, Memory) if needed.

Environment Variables

You can set environment variables to use throughout the pipeline:

• API keys, connection strings, and other sensitive information
• Environment-specific configuration values (development/production)