Skip to main content

Log

Logs the provided text with the specified log level.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

if ContinueOnError property is true, no error is caught when the project is executed even if Catch node is used.

Input​

  • Text - Text to be logged.

Options​

  • Log Level - The log level for the message. Available levels are: trace, debug, info, warn, error. The default value is 'info'.

How It Works​

The Log node outputs messages to both the runtime console and log files:

  1. The node receives input text to be logged
  2. Validates that a log level is selected (not empty or "_")
  3. Converts the input to a string format
  4. Writes to two destinations:
    • Runtime log with the specified level (visible in UI/console)
    • File log with mapped severity (info/trace/debug → Info, warn → Warn, error → Error)
  5. The message passes through without modification

Requirements​

  • Text input must be provided (can be any data type - will be converted to string)
  • Log Level must be selected (cannot be empty)

Error Handling​

Error CodeDescriptionSolution
Core.Flow.Log.ErrOnCreateFailed to parse node configurationVerify node configuration is valid JSON
Core.Flow.Log.ErrOnMessageMessage parsing failed during executionCheck that input message format is valid
Core.Flow.Log.ErrLevel"Log level must be selected"Select a log level from the dropdown (trace, debug, info, warn, error)

Usage Examples​

Example 1: Debugging Variable Values​

Log variable values during development:

Input Text: `Current customer: ${customerName}, Order total: ${orderTotal}`
Log Level: debug

Output: "Current customer: John Doe, Order total: 1250.50"

Example 2: Process Milestones​

Track important milestones in your automation:

Input Text: "Successfully processed 100 records"
Log Level: info

Output: Info log entry for audit trail

Example 3: Error Logging​

Log detailed error information:

Input Text: `API call failed - Status: ${response.status}, Error: ${response.error}`
Log Level: error

Output: Error log entry with full context

Usage Notes​

  • When Continue On Error is enabled, errors are not caught even if a Catch node is present
  • The log level determines both console output and file logging
  • All log levels (trace, debug, info) write to the Info file logger
  • Warn and Error levels write to their respective severity levels in files
  • Input can be complex objects - they will be converted to string representation
  • Logs appear in real-time in the Robomotion UI during execution
  • File logs are stored persistently for audit purposes

Tips​

  • Use trace for very detailed diagnostic information (rarely needed in production)
  • Use debug during development to track variable values and flow execution
  • Use info for general informational messages about process progress
  • Use warn for potentially problematic situations that don't stop execution
  • Use error for actual errors or critical issues
  • Include contextual information in log messages (variable values, step names, timestamps)
  • Use template strings to include variable values: Processing ${itemCount} items
  • Avoid logging sensitive information (passwords, API keys, personal data)
  • Consider log volume - excessive logging can impact performance
  • Use structured log messages for easier searching and analysis
  • Disable or remove debug/trace logs before deploying to production
  • Comment - For static documentation (not logged during execution)
  • Stop - For terminating with error/success status
  • Should Stop - For checking if flow should terminate