Error message not showing up in risk workspace, when on the glide modal page.

[poojithaven]

In the Risk Workspace, while creating a 'Risk Assessment Project' and creating ad-hoc risk and when risk statement i populated and clicked on save, the screen gets stuck on save and no error message is displayed. Is there a way to resolve this, I noticed there is a sys_ui_page created for this and error messages are appearing there when we try the try it option.

[yashkamde]

Hello @poojithaven ,

try creating the ad-hoc risk without linking to a Risk Statement first, save it.

then edit afterward to attach the Risk Statement. If that succeeds, the issue is specifically in the risk-statement association logic, not risk creation itself.

If my response helped mark as helpful and accept the solution.

[poojithaven]

Yes, rest scenario everything works, we need error message to show up for this particular scenario.

I have pasted the error from sys_ui_page.

[yashkamde]

can you confirm and capture the exact error from the sys_ui_page "Try It" banner and cross check it against System Logs (System Log > All) 

[Aravind2799]

Hi @poojithaven 

Thanks for the detailed repro steps - the fact that this only hangs once the Risk Statement field is populated, combined with the sys_ui_page showing a real error via Try It, is a strong clue.

What's likely happening:

Risk Workspace runs inside a sandboxed Now Experience UI (UI Builder), which doesn't support classic Jelly sys_ui_page popups opened via GlideDialogWindow. So when saving triggers a Business Rule or UI Action that tries to open one of these pages (commonly for duplicate-statement checks, risk scoring, or RAM assignment), the dialog silently fails to render inside the Workspace, and the save call just hangs with no error surfaced. Outside the Workspace, via Try It, the same page renders in classic context, so the real script error finally shows up.

A few things worth trying:

1. Save without the Risk Statement first, then edit the record afterward to add it. If this works, it confirms the issue is tied specifically to an insert-time trigger.
2. Create the risk from the classic list or form (sn_risk_risk table, outside Workspace) instead of the Risk Workspace UI. Classic forms support these dialogs fine, and the risk will still show up correctly back in Workspace afterward.
3. Check whether GRC: Risk Management Workspace and GRC: Advanced Risk Assessment are on their latest store app versions. ServiceNow has patched similar stuck-on-save issues in past releases.
4. If you have admin access, it's worth tracing which Business Rule or UI Action on sn_risk_risk references that sys_ui_page, and checking the exact error from Try It. That will tell you whether it's a scripting bug, an ACL block, or something else.
5. If none of the above resolves it, I'd recommend logging a ServiceNow Support (HI) case with the sys_ui_page sys_id plus the Try It error trace. If this turns out to be out-of-the-box behavior, it's likely a defect ServiceNow will need to fix rather than something to work around long-term.

Let us know if option 1 gets you unblocked in the meantime, that alone would help confirm the root cause.

Aravind Panchanathan 

Senior Technical Consultant