Definition and Usage
Print to log allows you to output a message or variable to the execution log. This action is useful for debugging purposes, tracking workflow progress, or displaying variable values during execution.
Parameter Values
Input parameters
Parameter | Description | Possible Values | Required | Options / Notes |
Log type | Select the log type | Information, Error, Warning | Yes | Determines how the message appears in the log |
Content to print | Enter the text or variable to print | Any text or variable | Yes | You can use static text, variables, or a combination of both |
Error handling
Parameter Name | Description |
Throw error & stop | When an error occurs, the action will trigger an error and stop the execution of the entire app. |
Retry command | If an error occurs, the action will retry the command in an attempt to resolve the issue and continue the process. |
Ignore error & continue | When an error occurs, the action will be ignored, and the workflow will continue without interruption. |
Variables produced
This action doesn't produce any variables.
Using Variables in Conditions
You can insert variables into the "Content to print" field by clicking the {x} button or typing the variable name enclosed in curly braces. This allows you to display dynamic values in your log messages.
For example, if you have a variable named "customerName", you can print it with additional text like: "Processing order for customer: {customerName}".
Notes
Log messages can be viewed in the execution logs after the workflow runs
Different log types (Information, Warning, Error) are displayed with different visual indicators in the log
This action is particularly useful for troubleshooting workflows and monitoring execution progress
Consider using descriptive messages to make logs more informative and easier to understand