Certification Tasks Not Fully Updating When Cancelling a Certification Instance<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue: When cancelling a certification instance (cert_instance), not all related certification tasks (cert_task) may transition to the expected state (e.g., state 7) as defined in the business rule. This typically occurs when the instance has a large number of associated tasks, potentially causing performance or timeout issues. Steps to Reproduce:Identify a cert_instance with a large number of related cert_task records.Cancel the cert_instance.Observe that only some of the related cert_task records transition to the expected state while others remain unchanged. Cause: The default business rule updates tasks individually, which may not complete successfully for a large number of tasks due to performance constraints.Legacy Data Certification is being deprecated, so some functionality may not be fully optimized for large datasets./sys_script.do?sys_id=6ef2b6929741300000f8d7b8fa297525&sysparm_record_target=sys_script&sysparm_record_row=2&sysparm_record_rows=6&sysparm_record_list=collectionCONTAINScert_%5Ecollection%3Dcert_instance%5EORDERBYcollection Workaround:Preferred approach: Use CMDB Workspace for ongoing certification management, as it replaces the legacy data certification functionality.Temporary workaround: For stuck certification instances, tasks can be updated in bulk using a script: var current_sys_id = current.sys_id;var task = new GlideRecord('cert_task');task.addQuery('cert_instance.sys_id', current_sys_id);task.addQuery('state', '!=', 3);task.setValue('state', 7);task.updateMultiple(); This ensures all tasks are updated in bulk, avoiding individual iteration and reducing performance impact.