User cannot view Catalog Task (sc_task) in the related list of an RITM<!-- /*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: User cannot view Catalog Task (sc_task) in the related list of an RITM CAUSE: After extensive additional debugging, we identified that the issue was related to timing in a custom Business Rule that creates the tasks. The business rule was modified from running on update to running on insert, and the approval logic was commented out.This change introduced a timing conflict: at the moment of insert and BR after insert, the RITM record is not yet fully initialized, its variables and other components are not fully available. As a result, the catalog task was being created in an incomplete or “invalid” state, which prevented users from viewing it. Despite everything visually looking correct. RESOLUTION: Reverting the logic back to an after‑update business rule and adding duplicate gating resolves the issue. While this approach is not ideal, the after-insert method consistently failed regardless of the data, user, groups, roles, ACLs, or other associated elements.