Description:

The Log Warning workflow step logs a warning message to the System log. It allows the workflow to specify the source of the warning, provide a detailed warning message, and optionally select a logging priority.

The step supports:

• Specifying the source of a warning.
• Providing a detailed warning message.
• Logging multiline warning information.
• Assigning an optional logging priority.
• Recording workflow warnings in the System log.
• Returning a True or False result for workflow routing.

Usage:

The Log Warning step is typically placed after a workflow activity when the workflow encounters a condition that should be recorded but does not necessarily represent a processing failure.

A typical workflow pattern is:

Workflow Activity → Log Warning → Continue Processing

For example:

Start
  ↓
Validate Request
  ↓
Log Warning
  ↓
Continue Processing

The multiline message input makes the step suitable for structured warning information containing multiple lines, such as processing details, record identifiers, workflow information, and the condition that generated the warning.

Typical Workflow Suggestions:

Log a Non-Critical Processing Warning

Use the Log Warning step when a workflow encounters a condition that should be recorded but does not require the workflow to stop.

Example:

Validate Request
      ↓
Check Optional Data
      ↓
   Warning
      ↓
Log Warning
      ↓
Continue Processing

Warning Source:
Request Validation

Warning message:
Optional customer information was not available.

Customer ID: {{CustomerID}}
Process Instance: {{InstanceID}}

Log Warnings from Integration Processing

Use Log Warning when an external integration completes with a condition that requires attention but does not prevent the workflow from continuing.

Example:

Prepare Request
      ↓
External API Call
      ↓
Check Response
      ↓
Log Warning
      ↓
Continue Processing

Warning Source:
Customer API

Warning message:
Customer record was returned without optional address information.

Customer ID: {{CustomerID}}
Request ID: {{RequestID}}

Log Detailed Multi-Line Warning Information

Because Warning message to log uses the multilineTextBox data type, the step can be used to record structured warning information containing multiple lines.

Example:

Warning Source:
Document Processing

Warning message:

Document processing completed with warnings.

Document: {{DocumentName}}
Document ID: {{DocumentID}}
Process Instance: {{InstanceID}}
Warning: Metadata field was not populated.
Action: Processing continued.

Log Warnings Before Continuing an Alternate Path

Use the step when a workflow detects a condition that requires an alternate processing path.

Example:

Process Request
      ↓
Check Request
      ↓
Log Warning
      ↓
Use Alternate Processing

Warning Source:
Order Processing

Warning message:
Primary processing option was unavailable.
The workflow will use the alternate processing path.

Record Warnings for Workflow Monitoring

Use Log Warning to record significant workflow conditions that may be useful when reviewing or monitoring process execution.

Example:

Start
  ↓
Process Data
  ↓
Log Warning
  ↓
Complete

Warning Source:
Data Processing

Warning message:
Three records were skipped during processing.

Process Instance: {{InstanceID}}
Processing Status: Completed with warnings

Example:

Let’s build and execute the “clsLogWarningDef” example.           

• Create a new definition named “clsLogWarningDef” and open it in designer mode. 
• Drag a "clsLogWarning" step to the canvas.
• Connect the dots between the “Start” and "clsLogWarning" steps, as shown above. 
• Select the line between the steps to configure the “Connection Properties”. The default property values are “None, True, False, Error, and Evaluate”. Depending on the step’s purpose, you can configure additional values.
• Click the "clsLogWarning" step to configure its “Required” properties. Provide a name for the step, the source of the warning message, and the text message to log. Then click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description. 

• Click the "clsLogWarning" step to configure its “Optional” properties. Select a priority from the dropdown list (Low, Medium, High). Then click the Save button. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

• Save the process definition, create a new instance, and execute it. As configured, the process step should log the warning message to the System log. Navigate to the Status—System log page and select the log by type and warning. 

Tips:

• Provide a meaningful Warning Source so that the origin of the warning can be identified easily.
• Include enough context in the warning message to make the log entry useful.
• Use the multiline message field to organize detailed warning information into readable sections.
• Include relevant workflow context such as process instance information, record identifiers, or operation details where appropriate.
• Use consistent warning-source names across workflows.
• Configure Priority when the workflow requires a specific logging priority.
• Avoid logging passwords, authentication tokens, secrets, or other sensitive credentials.
• Avoid unnecessarily logging confidential or sensitive business information.
• Use Workflow Variables where appropriate to include runtime information in the warning message.
• Test the warning message configuration before deploying the workflow.
• Verify the System log after execution to confirm that the expected warning was recorded.
• Connect the False path to appropriate error-handling logic.
• Test both successful and unsuccessful logging scenarios.
• Use consistent message formatting when multiple workflows write similar types of warnings.
• Keep warning messages specific rather than using generic messages such as A warning occurred.
• Include the operation or workflow activity associated with the warning where useful.
• Use Log Warning for conditions that require attention but are distinct from errors or failures.
• Verify the available logging-priority options in the FlowWright environment before documenting specific priority names.

Definition Sample:

You may download the sample definition and later import it into your FlowWright Process Definition (XML file) or Form Definition (HTML file).

Note: Verify and complete any missing configuration after importing the sample, including:

• Warning Source.
• Warning message to log.
• Priority.
• Workflow Variable references.
• Environment-specific logging configuration.
• Downstream True and False workflow paths.
• Any error-handling or notification activities.

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.