Logs

Two log streams, both configurable from /org:

1. System Logs — backend / platform operations
2. Logs (flow logs) — what the runtime captures from agent flow executions

System Logs management

Configure logging for microservice operations and backend system activities. Control which internal service events are captured.

#	Channel	Type	Available	Engaged	Description
1	System	Action	Yes	Yes	Audit trail of significant platform operations.
2	System	Debug	Yes	Yes	Detailed diagnostics for tracing and troubleshooting.
3	System	Info	Yes	Yes	Routine informational messages from the platform.
4	System	Warning	Yes	Yes	Potentially problematic conditions that don't stop execution.
5	System	Error	Yes	Yes	Failures and error conditions reported by system services.

Logs management (flow logs)

Configure logging for AI flow executions. Control which log levels are captured during agent flow runs.

#	Channel	Type	Available	Engaged	Description
1	Log	Debug	Yes	Yes	Detailed diagnostics for tracing and troubleshooting.
2	Log	Info	Yes	Yes	Routine informational messages from flow execution.
3	Log	Warning	Yes	No	Potentially problematic conditions during flow execution.
4	Log	Error	Yes	Yes	Failures and error conditions during flow execution.

Toggling

Each log row can be engaged (capturing) or disabled (silenced) — except:

• Error logs cannot be disabled. That row is always on, in both streams. This is a deliberate floor — when something fails in production, you want the error trail.

How this connects to flow code

The flow-side log stream is what LogMgr writes into from inside Script Nodes:

import LogMgr from 'system/log';

export async function exec() {
    LogMgr.debug('...');    // captured iff Log/Debug is Engaged
    LogMgr.info('...');     // captured iff Log/Info is Engaged
    LogMgr.warning('...');  // captured iff Log/Warning is Engaged
    LogMgr.error('...');    // ALWAYS captured (cannot be disabled)
}

What the runtime actually persists is whatever's marked Engaged here. So if you've disabled Log/Debug, calls to LogMgr.debug from your scripts are still made — they just don't get saved.

Related

• Script Node — Log API — how to write to the flow-side log stream from inside a Script Node.