Logs page

There are two levels of logging in the platform:

  • The Executions page includes a single record for every execution in the selected workspace

  • The logs page lists all the logs for all the flows in the selected workspace.

Searching & filtering logs

Choose to filter by one or more parameters to concentrate on specific logs.

By Search
  1. Type a search term to find it in the list.

  2. Click Clear to remove the search term and return to the default view.

By Name
  1. Click the Flow name drop-down

  2. Select the desired flow(s) using the checkboxes.

  3. Click the Apply button to only review the logs of the chosen flows.

  4. Click the Clear button to unselect all flows.

By Time
  1. Use the interval/calendar filter to find executions from a specific timeframe which may span months or minutes.

  2. Click Apply to apply the filter or Clear to discard all selections.

By Log level

Click the Log level button to restrict which logs are displayed by selecting the desired level(s). This enables you to focus on and troubleshoot errors of a specific type like error, debug etc.

The log levels are:


This filter includes all other log entries for which the log level is not set. These logs are usually generated by the platform root processors or included code libraries.


Outputs everything your component can show, including elements of the data passing through the component. This should be used with extreme caution and for limited periods


Designates fine-grained informational events that are most useful to debug an application.


This is the default setting and is recommended for use in production flows. Info level logs are added providing information on successful executions. No confidential data is included in these logs.


Warning level messages are logged. A warning does not indicate a flow has failed, but is indicative of a possible future issue.


The logs only include errors. An error indicates that a flow has actually failed.


Severe error that will prevent the flow execution from continuing. This error indicates a major platform problem.

Debug and trace level logs may render data passing through the component as plain text. This should be used with extreme caution and for limited periods. Always check your logging levels before moving a flow from staging to production.