System Variables

Templates -
System Variables Introducing system variables information about your scenario current execution team and organization is now available in reusable elements that can be mapped to any module simply click on a module.

Field open the custom and system variables tab and under the scenario variables section click on any element to add it to the field system variables can make error handling.

And scenario activity tracking easier and faster than ever before here's an example in this scenario an error handler route has been added at the slack module.

In the case an error occurs while this module is being executed a new row will be created in a google sheet with the goal to keep track of the error and all the information associated with that.

Particular scenario execution the information about the scenario execution is mapped to the new spreadsheet row using system variables knowing the scenario name id and url can.

Help you instantly identify where the error came from the execution id and execution start date will help you dive deeper into your scenario history logs and find the execution that caused the.

System Variables

Error so you can resolve any issues and make sure that it doesn't happen again system variables can also help you keep track of how many operations your scenarios consume and interrupt.

Executions that are operation intensive here's an example this scenario retrieves all the newly updated records from an air table base and for each one performs a series of actions a filter.

Has been added after the http module to check if more than 20 operations have been consumed up until that stage the number of operations is retrieved using the operations consumed system.

Variable which is mapped in the filter condition field in the case where more than 20 operations are performed during an execution of this scenario the filter condition will not be met and the.

Posts Related:

Tags:
Previous Post Next Post