Sign in

Error Handling Strategy

1 min read

The rule execution engine supports two types of errors with different behaviors:

Error Type
Behavior
When to Use
SOAP Fault
Continue running other rules; all warnings shown at end
Business condition failures (e.g., user not found)
Exception
Stop execution immediately; workflow creation fails
System failures (e.g., null references)

Error Logging

All rule execution is logged with “WAR:” prefix:

  • WAR: Executing rule [RuleName] for [Target]
  • WAR: Rule [RuleName] completed in [X]ms
  • WAR: Warning - Rule [RuleName] returned error: [Message] (SOAP Fault)
  • WAR: Error - Rule [RuleName] threw exception: [Message] (Exception)

Configuring Log Level for Workflow Assignment Rules:

To enable detailed logging for Workflow Assignment Rules execution, add the following configuration to the server’s appsettings.json file:

“LoggerConfiguration": {
“MinimumLevel": {
“Default": “Fatal”,
“Override": {
“Aras.UnifiedChangeManagement.WorkflowAssignmentRules": “Debug”
}
}
}

Log levels available:

  • Debug: Logs all WAR execution details, timing, and results
  • Information: Logs rule start and completion
  • Warning: Logs only SOAP Fault errors
  • Error: Logs only Exceptions
  • Fatal: Logs only critical Aras Innovator failures
Note
The “Fatal” log level is available for detailed logging of Workflow Assignment Rules only in Aras Innovator Release 34 and higher.