Skip to main content
Overview Of The WorkFlow Page
Ilya letnik avatar
Written by Ilya letnik
Updated this week

The Flow page includes various options and functionalities that will help you create the automation efficiently and according to your requirements.

Workflow Mode - Fast/Safe
By default, flows run in chronological order and are set to “Safe” mode. However, if your workflow is independent of other workflows or doesn’t require execution in a specific order, we recommend switching to “Fast” mode to ensure your workflow is initiated faster after being triggered.


Active/Inactive
You can deactivate flows that are no longer needed to prevent them from running. If necessary, you can always reactivate them by setting the flow back to “Active.”

Editor tab
The Editor tab is where you design your automation by selecting the appropriate trigger and defining the subsequent steps.


Runs tab
Each time the flow is activated, it counts as a single run, and all runs are listed under the Runs tab.

The runs are categorized as follows:

Active Runs: Runs that were executed in full.

Archived Runs: Runs that were stopped because the conditions defined at the beginning of the flow were not met and were subsequently archived.




Variables
Instead of using hard-coded data, you can define variables outside of the scripter step that can be easily adjusted upon need without having to adjust the script.


Once the variables are defined you can use them in various steps:



Secrets
Store keys securely for managing flows, widgets, and integrations with other platforms.
These keys can be used in the scripter step.



Drag and Resize Functionality
Resize the two sections of the page, editor and logs, to better focus on the content you need.

Debugging tips:

While creating a new step (or updating an existing one), there are a few useful tips that can help the process:

  1. Use the "Re-run" buttons to quickly reactivate the trigger without going back to Labguru and reproduce the trigger. Re-runs are available in the corner of any log - either in the 'Editor' or 'Logs' tabs.

  2. Turn "When stopped archive?" in all condition steps to False to avoid logs being missed due to being wrongly archived. Once a condition was verified to be written properly, turn "When stopped archive?" to True if needed (to reduce the "noise" of irrelevant runs from the log).

  3. Add Variables logger steps to verify variables were stored properly.

  4. Use the log function in Lab scripters that are not working to better locate the problematic line.

Did this answer your question?