Executing Workflows

Configure, run, and monitor your workflow executions

Overview

Executing a workflow means running all the test scripts (blocks) in the order you've defined. Once you execute a workflow, Test Orchestration runs each node sequentially, captures results, and generates reports.

✅ Prerequisites

Before executing, ensure you've completed:

• ✓ Created a Project

• ✓ Created a Workflow with at least 2 connected blocks

• ✓ Set run configuration (environment, browsers, devices)

This guide covers:

• 🎯 Running workflows manually

• ⏱️ Monitoring execution in real-time

• 📊 Understanding execution states

• 📈 Viewing results and logs

Estimated Time: 5 minutes to execute and review results

---

Execution Methods

Test Orchestration offers multiple ways to execute workflows:

Manual Execution

Run Now - Execute Immediately

Execute your workflow right now with one click.

Best For:

• Development and testing

• Quick validation

• Ad-hoc test runs

• Debugging workflows

When to Use:

• Testing new workflows

• Validating changes

• Checking specific functionality

• Quick smoke tests

Scheduled Execution

CI/CD Integration

---

Step 1: Open Your Workflow

1

Navigate to Workflow

1. Go to Projects in sidebar

2. Select your project

3. Click on the workflow you want to execute

You'll see the workflow canvas with all your blocks.

2

Verify Workflow

Before executing, quickly verify:

• All blocks are connected properly

• No disconnected blocks (unless intentional)

• Workflow is saved (check for unsaved changes indicator)

Unsaved Changes: Save your workflow before executing to ensure you're running the latest version!

---

Step 2: Configure Run Settings

Click the "Run Configuration" or "Settings" icon (usually a gear ⚙️ icon near the Execute button).

Configuration Options

Environment

Select Environment

Choose the target environment for execution:

Environment	Description	Use Case
Development	Dev environment	Active development, debugging
QA/Testing	QA environment	Pre-release testing
Staging	Production-like	Final validation before release
Production	Live environment	Production monitoring, smoke tests

Production Warning: Be extremely cautious when running tests against production. Consider read-only tests or use dedicated test accounts.

Environment Variables: Each environment may have different:

• API endpoints/URLs

• Database connections

• Credentials

• Feature flags

• Configuration values

These are automatically applied based on your selection.

Browsers (Web Tests)

Devices (Mobile Tests)

Advanced Settings

Configuration Presets

Save Time: Create configuration presets for common scenarios (e.g., "Chrome + Firefox + Edge", "All Mobile Devices", "Production Smoke")

To save a preset:

1. Configure all settings

2. Click "Save as Preset"

3. Name it (e.g., "Cross-Browser Desktop")

4. Reuse later with one click

---

Step 3: Review Execution Plan

Before running, review what will execute:

Execution Summary

Pre-Execution Summary

The system shows:

Blocks to Execute:

• Total number of blocks

• Estimated duration

• Service types involved (API, Web, Mobile, Desktop)

Configuration:

• Selected environment

• Browsers/devices

• Timeout settings

Estimated Completion:

• Start time

• Estimated end time

• Sequential execution

Resource Requirements:

• Browser/device instances needed

• Execution credits (if applicable)

• Storage for artifacts

Execution Order

---

Step 4: Execute the Workflow

Time to run! 🚀

1

Click Execute Button

1. Find the "Execute Workflow" button (▶️ play icon)

2. Button is usually in the top-right of the canvas

3. Click it to start execution

2

Confirm Execution

A confirmation dialog appears showing:

• Workflow name

• Environment

• Browsers/devices

• Estimated duration

• Any warnings or notes

Review and click "Execute Now" or "Run"

3

Execution Starts

The workflow begins executing immediately!

What Happens:

1. Workflow queued in execution engine

2. Resources allocated (browsers/devices)

3. First step starts executing

4. Real-time updates appear on canvas

---

Step 5: Monitor Real-Time Execution

Watch your workflow run in real-time on the canvas.

Execution States

Step States

Understanding Step Colors

Each step changes color to show its current state:

State	Color	Icon	Meaning
Queued	⚪ Gray	⏸️	Waiting to start
Running	🟡 Yellow	▶️	Currently executing
Passed	🟢 Green	✅	Completed successfully
Failed	🔴 Red	❌	Execution failed
Stopped	⚫ Black	🛑	Manually stopped
Skipped	⬜ Light Gray	⏭️	Skipped due to conditions
Retrying	🟠 Orange	🔄	Retry in progress

Visual Indicators

Steps also show:

• Progress bar: Percentage complete

• Elapsed time: How long it's been running

• Status icon: Quick visual indicator

• Pulse animation: Active execution indicator

Execution Progress

Live Logs

Live Monitoring Controls

While executing, you have controls:

Pause/Resume

Pause Execution

To Pause:

1. Click "Pause" button (⏸️)

2. Current step completes

3. Workflow pauses before next step

When Paused:

• Review logs

• Check results so far

• Adjust settings (if needed)

To Resume:

1. Click "Resume" button (▶️)

2. Execution continues from where it paused

Stop

View Details

---

Step 6: View Execution Results

Once execution completes, review the results.

Immediate Results (On Canvas)

Success

Successful Execution ✅

When all steps pass:

Visual Indicators:

• All steps are green 🟢

• Success message at top

• Overall status: PASSED

• Total execution time displayed

Summary Shows:

• ✅ Total steps: 8

• ✅ Passed: 8

• ❌ Failed: 0

• ⏱️ Duration: 3m 42s

Quick Actions:

• Download report

• Share results

• Schedule next run

• View detailed report

Congratulations! All tests passed successfully. 🎉

Failure

Partial

Detailed Step Results

Click any step to see comprehensive results:

Execution Info

Basic Information

• Status: Passed/Failed/Skipped

• Duration: Exact execution time

• Start Time: When step started

• End Time: When step completed

• Retry Attempts: If retries occurred

Environment Details

• Browser/Device: What was used

• Environment: Staging/Production/etc.

• Version: App/script version

• User: Who triggered execution

Logs & Output

Artifacts

Data Flow

Errors

---

Step 7: Access Full Report

For comprehensive analysis, view the full report in the Reports section.

1

Navigate to Reports

Click "Reports" in the left sidebar navigation.

2

Find Your Execution

Your workflow execution appears at the top (most recent).

List Shows:

• Workflow name

• Status (Passed/Failed)

• Date/time

• Duration

• Environment

• Triggered by

3

Open Detailed Report

Click on the execution to view comprehensive report.

See Reports Documentation for full details.

---

Execution Best Practices

Before Execution

Pre-Flight Checklist

• Workflow is saved

• All blocks are connected

• Run configuration is set

• Correct environment selected

• Test data is available

• No one else is using test accounts (if shared)

During Execution

Do:

• ✅ Monitor progress for first few runs

• ✅ Watch for patterns in failures

• ✅ Take notes on issues

• ✅ Let it complete before making changes

Don't:

• ❌ Edit workflow while it's running

• ❌ Stop execution unless necessary

• ❌ Run multiple instances with same test accounts

• ❌ Ignore warnings in logs

After Execution

Always:

1. Review results (even if passed)

2. Check execution time trends

3. Look for warnings in logs

4. Download artifacts if needed

5. Share results with team

6. Update workflow if issues found

---

Troubleshooting Common Issues

Workflow stuck in "Queued" state

Possible Causes:

• Execution queue is full

• Insufficient resources (browsers/devices)

• No available execution credits

• System maintenance

Solutions:

• Wait for queue to clear

• Check execution credits balance

• Contact admin about resources

• Try again later

Step fails immediately

Check:

• ✅ Script exists and is accessible

• ✅ Correct environment selected

• ✅ Required data from previous step

• ✅ Network connectivity

• ✅ Permissions

Solutions:

• Review error message

• Check input data

• Test script individually

• Verify environment configuration

Timeout errors

Common Causes:

• Network latency

• Slow server responses

• UI elements loading slowly

• Incorrect selectors

Solutions:

• Increase timeout values

• Add Wait actions

• Optimize selectors

• Check network conditions

• Use explicit waits instead of sleep

Can't see execution results

Check:

• ✅ Execution has completed

• ✅ Page is refreshed

• ✅ Correct project/workflow selected

• ✅ Permission to view results

Solutions:

• Refresh the page

• Check Reports section

• Verify permissions

• Clear browser cache

"Resource unavailable" error

Causes:

• All browsers/devices in use

• Environment temporarily down

• Network issues

• Service outage

Solutions:

• Wait and retry

• Use different browser/device

• Check system status page

• Contact support if persistent

---

Execution Metrics to Watch

Key Performance Indicators

Metric	Good	Warning	Critical
Pass Rate	>95%	90-95%	<90%
Avg Duration	Consistent	+20%	+50%
Failure Frequency	Occasional	Frequent	Constant
Timeout Rate	<1%	1-5%	>5%

Trend Analysis

Monitor over time:

• Pass Rate Trend: Should be stable or improving

• Execution Time: Should be consistent

• Failure Patterns: Identify flaky tests

• Resource Usage: Track consumption

---

Quick Reference

Execution Commands

Action	Location	Shortcut
Execute Now	Top bar	Ctrl/Cmd + Enter
Pause	During execution	Ctrl/Cmd + P
Stop	During execution	Ctrl/Cmd + Shift + S
View Logs	Bottom panel	Ctrl/Cmd + L
Full Screen	Canvas view	F11

Step States Quick Guide

⚪ Gray    → Queued (waiting)
🟡 Yellow  → Running (active)
🟢 Green   → Passed (success)
🔴 Red     → Failed (error)
⚫ Black   → Stopped (halted)
⬜ Lt Gray → Skipped (bypassed)
🟠 Orange  → Retrying (attempting again)

What's Next?

Workflow Executed! 🎉 Now explore more features to enhance your testing.

Continue Learning:

• Data Propagation - Pass data between workflow steps

• Scheduler - Automate execution with schedules

• Action Types - Add advanced actions to workflows

• Reports - Analyze test results and trends

• Folders - Organize your workflows

• Session Persistence - Maintain state across steps

Next Steps:

1. View your execution report - Analyze the results

2. Schedule recurring runs - Automate your testing

3. Explore data propagation - Learn about data flow

4. Read about advanced topics - Conditional logic and more

---

Need Help?

Have questions about execution? Reach out to our support team!

Resource	Description
💬 Live Chat	Instant support
📧 Email	Detailed inquiries
📚 Knowledge Base	Common issues

---

Next: Learn about organizing workflows with folders →