Test runs
A test run executes your workflow with sample data so you can confirm it behaves the way you expect — before it's handling real events.
Running a test
In the builder, start a Test Run. OrchaSync queues the run and begins executing it. As each node runs, it lights up on the canvas:
| Ring | State |
|---|---|
| (none) | Idle — hasn't run yet |
| 🔵 Blue | Running |
| 🟢 Green | Finished successfully |
| 🔴 Red | Errored |
Inspecting a node
Click a node after (or during) a run to inspect:
- Input — the data the node received.
- Output — the data it produced.
- Error — the message, if it failed.
This is the fastest way to find where a workflow is going wrong: follow the nodes until you hit the red one, then read its error and input.
Tips
tip
If a run seems to hang, check that every path reaches an End node — an unterminated path never signals completion.
tip
Use a Message node to feed known sample data into a test run while a real connection isn't set up yet.