Overview
Workflow testing in the editor is centered around Run Workflow, Live Progress, and Start a new Workflow Run. The run sheet shows step progress and output for the workflow run that is currently active. You can also run an individual step from the canvas when you want a smaller test while you are still editing the workflow.How do I start a workflow run in the editor?
Open the workflow in the editor. Click Run Workflow in the header. This opens Live Progress. It does not start the workflow by itself. In Live Progress, click Start. Fetch Hive opens Start a new Workflow Run. Click Start Workflow Run to begin the run. If your Start step has inputs, the modal shows a field for each variable so you can enter test values before the run starts. Array start inputs use a JSON textarea and must contain a valid JSON array before the run can start. Use the sample input actions next to a start input when you want to load a saved test value or save the current value for later runs. If a Start input has an Example value, the example only helps you build the workflow in the editor. The run modal still requires the real value you want to test; examples are not copied into the run.Where do I see results from a workflow run?
After the run starts, keep Live Progress open. Use the Progress tab to review step completions for the active run. Running completions can appear before they finish, so this tab is useful while the workflow is still executing. Use the Output tab to inspect the active workflow run’s current output. The output view can render different result types. In the reviewed UI, image outputs render as images, PDF outputs render as a download link, and other results render directly in the sheet. If no output is available yet, the sheet shows a waiting state while the run is active. After the active run finishes, the sheet keeps that run visible so you can review its final step results and output. Use workflow logs for older run history. If a workflow reaches a Human in the Loop step, the run is paused while it waits for the recipient’s choice. Paused runs do not occupy Live Progress, so you can start another editor test run while the human choice is pending. Open the paused run from workflow logs to see why it is waiting and to access the choice page.How do I test start inputs and repeat runs while iterating?
Define your variables on Start first. Each time you open Start a new Workflow Run, Fetch Hive uses those Start inputs to build the run form. Text inputs accept plain text, while array inputs accept JSON arrays such as["one", "two"].
Load a saved sample input when you want to restore a known test case quickly. Save the current value as a sample input when you want to reuse it in later workflow runs or prompt tests.
Use array examples on the Start step when you want to configure an Iteration before the source input has ever been submitted. The editor can preview the first example item and expose its fields for variable insertion, but each run still uses the array you enter in the run form.
Change the input values in the modal when you want to test the same workflow against a different case without changing the workflow structure itself.
This is the safest way to repeat runs while you are tuning prompt content, step settings, or failure behavior.
How do I test a single step while I edit?
Hover over a step node on the canvas. Click Run Step to start a test for that step. For AI Prompt steps, the step settings header also includes Run, and the right side of the sheet shows the prompt messages and model response for that step test. Use step tests for quicker iteration when you do not need to run the full workflow every time. Single-step tests resolve variables from the active workflow run when one exists. If a Start input has no real run value yet, the step test can use that input’s Example value as an editor-only fallback, including indexed array paths such as{{feeds.0.url}} or wildcard paths such as {{feeds.*.url}}.