Debugging a flow
Sometimes your flows won't work as expected, and you'll need to dig a bit deeper. Here are some ways to help debug your flows.
The Step button allows you to run a single command at a time:
You can use the Step button to check the result after each command and make sure that each step works as expected.
If you find that your flow works correctly when you step through the flow, but that it breaks when you run it normally, this might mean that there is a race condition. In other words, Browserflow may be performing actions before the website can properly handle it.
One way to work around this is to add
Waitcommands to make Browserflow wait after a command before proceeding. If you encounter this scenario, it may be indicative of an issue with Browserflow — please report it as an issue.
If you want to test only a few steps of your flow, you can disable commands to skip them when your flow is run:
Waitcommand can be used as a breakpoint by selecting "Wait until resumed" as the type. This command will pause the flow until it is resumed by clicking "Run" or "Step". It is useful for running the flow until a certain point.
The "Wait until resumed" type for the
Waitcommand is a temporary solution for supporting breakpoints and will likely be removed at some point in favor of an improved solution.
The console provides information that's useful for debugging your flow.
The logs tab shows a record of all commands that have been run and any errors:
Clicking on a log message will highlight the command that was running at the time.
The variables tab shows the current value of each variable:
Stepping through the flow and inspecting the variables is often helpful for identifying issues with a flow.