Simulation and events

One-shot simulation

Select this mode and click Execute to run the blueprint. The studio determines the execution order and propagates results between blocks. This mode suits a one-off task or the evaluation of a workflow.

It actually executes the configured integrations. Simulation mode does not disable file writes, commands, or calls to providers.

Active runtime

Select Active runtime and click Run to prepare and start the workers. Then use the contextual actions of compatible blocks to publish an input or trigger processing. Stop shuts down the runtime.

Blocks reactivate according to their inputs and triggering rules. This mode is event-driven; the time an agent or API takes still depends on its provider. It does not guarantee an execution deadline.

Edit an active workflow

Topology changes, such as adding connections or ports, require you to stop the runtime. You can still move blocks visually.

Blocks that support it can receive configuration changes while a run is loaded. These changes apply on their next activation without altering an execution that has already started.

Choose the right mode

1. A summary you need to produce once: start with One-shot simulation.
2. A workflow that needs to respond to several successive publications: choose Active runtime.
3. A structural change: stop the runtime, edit the connections, then restart it.
4. A result you want to keep: export it before starting a new simulation or using Reset.

Inspect before moving on

Check outputs and logs at important steps. A block can finish successfully while producing incomplete content. Add format and content checks that match your objective.