Lifecycle Events Logging - Zurich ReleaseSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Overview The Zurich release introduces enhanced Lifecycle Events (LE) logging capabilities designed to improve root cause analysis, reduce support dependency, and empower administrators with deeper visibility into LE Cases execution and failures. This feature is part of the HRSD Lifecycle Events module and is available to users with the sn_hr_le.admin role. Key Capabilities 1. Execution Logging Admins can now view execution logs directly within LE Cases by selecting Show execution logs from the Related Links section. This applies to both Workflows and Flow Designer executions. 2. Log Levels Logging supports four cascading levels: None – No logs captured.Error – Only error logs.Info (default) – Captures both informational and error logs.Debug – Full trace logs for deep diagnostics. The logging level is driven by System Property sn_hr_le.log_level (/sys_properties.do?sys_id=9b46aa07ff03121007edfffffffffff8) 3. Log Content Each log entry includes: MessageSource identifiersActivity sets contexts and ActivitiesTimestamps Use Cases Troubleshooting Failures: Identify exactly where and why an LE Case failed, including cases where workflows exceed execution limits, or Activities/Activity Sets haven't triggered due to Audience criteria not being met.Self-Service Enablement: Customers (LE Admins) can now diagnose issues independently, reducing the need to contact ServiceNow Support.Audit and Compliance: Logs provide a traceable history of LE execution, supporting governance and audit requirements. Activation, Access & Retention Availability: Lifecycle Events logging has been introduced in the Zurich releaseAccess Control: Only users with the sn_hr_le.admin role can view execution logs.Logs location: Logs are stored in the HR Lifecycle Events Case Logs table [sn_hr_le_case_log] and can be accessed via the LE Case form (from the Show execution logs Related Link).Retention: Logs for any specific LE Case are deleted when the case is inactive and hasn't been updated in 30 days. The Table Cleaner "sn_hr_le_case_log" (sys_auto_flush.do?sys_id=7a017ae2ff93121007edfffffffffffa) is responsible for this. For more details, refer to the Lifecycle Events logging product documentation page. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Lifecycle Events logging