Execution Log

The Execution log displays script runs allowing you to monitor executions, track statuses, and debug errors if they occur.

Access to the execution log is available to users with the Workspace privilege and W (Write) access rights.

To open the execution log, click the gear icon in the bottom left corner and select the corresponding option.

Execution Log Profile

The log displays:

• Execution statuses:
  • Running (trigger executed)
  • Completed (all blocks executed)
  • Error (an error occurred in a block)
  • Stopping (script stop was initiated)
  • Stopped (script was stopped)
• Start time of script execution
• Duration — (time from trigger activation to status assignment)
• Workspace where the script is located
• Script name

An activated script appears in the execution log when its trigger — the first block in the script — is executed.

The execution can be completed:

• When all blocks in all branches have been executed
• If an error occurs while executing all branches
• If the user stops the script

The Error status is registered in two cases:

• The block with an error prevents further execution
• The block with an error does not prevents further execution and all blocks are continue running

A script can be stopped only while in the Running status.

The execution log is cleaned regularly:

• All entries older than 7 days are deleted
• If more than 250 entries exist for a script version, the earliest ones are deleted even if they are less than 7 days old

Working with the Execution Log

You can search by script name and filter entries by period, workspace, and status.

You can also sort the entries by:

• Recency (the Time column)
• The alphabetical order (the Workspace and Script columns)
• Duration (the Duration column)

Viewing Script Execution

Clicking a log entry opens the script scheme. The header displays:

• Name and version
• Status
• Date and time
• Duration

The script scheme consists of action blocks and connections. Each block can be in one of the following states:

• Block executed (you can view the input and output data of the selected block; input data of the trigger is always available)
• Error in block
• Block belongs to the execution, but its data is not available for viewing
• Block does not belong to the execution and cannot be selected for viewing

Data between blocks is displayed in JSON format.

When processing batch data from a database, the left panel shows the first 10 records and the total number of records in the batch for both input and output.

The Error in Block State

If a block has output data in the Error in block state, the Error tab is added to the left panel. If there is no output data, the Error tab replaces the output tab.

In case of an error, the script card in the workspace shows the number of errors that have occurred in the past seven days and the current day.