Console Log

At the bottom of the workspace, you'll see the console log, where all log messages are displayed. Whenever you perform an action in the workspace, run a script manually, or trigger a script through a scheduled or external event, the related logs will appear in the console log.

Expand/Collapse console log panel

You can resize the console log panel by using the splitter between the console log and the rest of the workspace. To expand the console log to full screen, click the first button in the console log header. 

Click the same button again to collapse it back from full screen.

Expand/Collapse log messages

If a log message contains multiline text, a caret will appear in front of it. Click the caret to expand the message into a multiline view, which is useful for reading structured logs, such as JSON data.

Click the caret again to collapse the message back to single-line format.

Information display options

By default, the following fields are displayed at the top of each log message:

  • Date: The date when the message was received.
  • Time: The time when the message was received.
  • Source: Where the message originated from (e.g., Workspace for actions you took, or the script name for triggered scripts).
  • Environment Name: The name of the environment where the script was invoked.
  • Invocation ID: A unique ID for the script invocation.

Customize the log fields 🪵

Use the second button in the console log header to select which of these fields you want to display.

Filter by log-message type

Each log message has a type: Debug, Information, Warning, Error, or Success. Use the third button in the console log header to filter logs by type. If no filter is selected, all log messages will be displayed.

Toggle live feedback

If you're troubleshooting or developing on a workspace that actively receives events from an external system, you might see log messages from script invocations you didn't trigger. To filter out these sometimes noisy messages, uncheck the Live Feedback checkbox in the console log header. This will only display messages from scripts you trigger manually.

This is useful if you're troubleshooting or developing in a workspace that actively receives events from an external system. It can also help when you're triggering scripts manually or via event listeners using test event payloads and want to filter out messages from external events.

Filter log messages by environment

By default, log messages are shown only for the environment selected in your workspace. To see all log messages, regardless of the environment, uncheck the Filter by Environment checkbox in the console log header.

Search log messages by keyword

To filter messages by a specific keyword, use the search box on the right-hand side of the console log header.

Clear log messages

At any time, click Clear Log to clear all log messages. 

Abort script limitation 🚨

The only way to abort a script invocation is to click Abort Invocation in the Invocation Scheduled section of the log. If you clear the console, you lose the opportunity to abort any currently running script invocation. Clear logs with caution!



On this page