Blazing iconBlazing
Coming SoonDev Preview

This content is part of an upcoming preview program. Request early access

Quick Start

Edit on GitHub

Get started with Flow Sandbox in minutes

Flow Sandbox provides an isolated environment for developing, testing, and debugging Blazing Flow workflows without affecting production systems.

What is Flow Sandbox?

Flow Sandbox is an isolated workflow orchestration environment that lets you:

  • Test workflows without affecting production
  • Debug issues with detailed execution traces
  • Develop faster with instant feedback
  • Validate changes before deploying to production
  • Replay scenarios to reproduce and fix bugs

Prerequisites

Before you begin, ensure you have:

  • A Blazing Core account
  • Blazing CLI installed (npm install -g @blazing/cli)
  • Basic understanding of Blazing Flow
  • Node.js 18+ or Python 3.8+

Installation

Install Blazing CLI

Bash

Authenticate

Bash

Create Your First Sandbox

1. Initialize Sandbox

Create a new sandbox environment:

Bash

This creates an isolated environment with:

  • Dedicated workflow executor
  • Isolated state store
  • Separate event queue
  • Independent metrics

2. Configure Sandbox

Create a sandbox.yaml configuration:

YAMLDev PreviewL3

Apply the configuration:

Bash

3. Deploy Workflow to Sandbox

Deploy a test workflow:

Python

Deploy to sandbox:

Bash

4. Run Workflow in Sandbox

Execute the workflow:

Bash

You'll see real-time execution output:

TEXTDev PreviewL1

5. Inspect Execution

View detailed execution trace:

Bash

This shows:

  • Task execution timeline
  • Input/output for each task
  • State changes
  • Error details (if any)
  • Resource usage

Development Workflow

Local Development

Run sandbox locally for faster iteration:

Bash

Testing Workflows

Write tests using the sandbox:

Python

Run tests:

Bash

Debugging Workflows

Enable debug mode for detailed logging:

Bash

Sandbox Modes

Isolated Mode (Default)

Complete isolation from production:

YAMLDev PreviewL1
  • Workflows run in complete isolation
  • No interaction with production systems
  • Safe for testing breaking changes

Mirror Mode

Mirror production events for testing:

YAMLDev PreviewL1
  • Receive copy of production events
  • Test with real data patterns
  • Validate changes against live traffic

Hybrid Mode

Combine isolation with selective production integration:

YAMLDev PreviewL1

Environment Management

Create Multiple Sandboxes

Create sandboxes for different purposes:

Bash

List Sandboxes

Bash

Output:

Plain Text

Switch Between Sandboxes

Bash

Data Management

Reset Sandbox State

Clear all state and start fresh:

Bash

Export Sandbox Data

Export workflow executions for analysis:

Bash

Import Test Data

Load test data into sandbox:

Bash

Integration with CI/CD

GitHub Actions

YAML

Best Practices

1. Use Descriptive Names

Bash

2. Set Resource Limits

YAMLDev PreviewL1

3. Auto-Cleanup

YAMLDev PreviewL1

4. Use Version Control

Bash

Next Steps

Troubleshooting

Sandbox won't start

Check resource quotas:

Bash

Workflows fail in sandbox but work in production

Compare configurations:

Bash

Slow execution in sandbox

Increase parallelism:

YAMLDev PreviewL1

Getting Help