Automation basics

Reading a run's log

Find out what a run did and which block stopped it, and run again from there.

Runs on a profile are recorded. Press Logs in the editor's toolbar for this workflow's earlier runs, or open the Logs page and its Workflow runs view for every workflow.

Open a run to see its log. The top shows the profile and how long the run took. A failed run says Failed on and the block's name, with the error message and a button, Open this block in the editor.

Below is one line per block, in the order they ran: the time, the block's name, how long it took, its status, and its message or Description. The failed block is marked. Double-click a line, or press the arrow at its end, to show that block in the editor.

Click a line to see Log data: the data that block ran with. The menu beside it narrows the view to Loop data, Variables, Google Sheets, Previous block data or Replaced value. Replaced value shows what each {{...}} in the block's fields became, which is where a wrong reference shows up. Right-click a value to copy it, or to copy the reference that reads it, such as {{variables.email}}.

If a run shows no lines, the workflow has Save workflow log turned off in its Settings.

In WarpX Phone each run is recorded under the phone it ran on, and the log names the phone where WarpX Browser names the profile.

To try a fix without starting over, hover the block and press Run workflow from here. Blocks before it are skipped, so values they would have set are missing.

The Assistant panel in the editor offers one more way while a block is open in the sidebar: Run to here runs from the start up to that block and leaves the browser there. The block you have open is also the assistant's marker — it will not change anything that runs before it, and its own attempts start there.