Disable "NowAssist needs your input" notifications

Erik Nelson
Mega Sage

Hello!

 

We've recently started getting notifications (bell icon on the UI) stating "NowAssist needs your input". We currently don't have anything beyond a couple Creator licenses and I've turned off everything I can find, and yet they appear. They aren't setup as an email notification and I can't seem to locate anywhere else they might be setup. It does appear they're related to approvals specifically. They don't link to anything though and continue to appear. Does anyone know how to disable that functionality?

 

Thanks,

Erik

1 ACCEPTED SOLUTION

Brian Bakker
ServiceNow Employee

@Erik Nelson 

Did you raise the case? The defect "NowAssist needs your input" platform notifications appearing unexpectedly from NAP" has been raised and they are working on the fix. Unfortunately, the KE article (KB3227802) with the workaround provided in a Remote Update Set is INTERNAL. Please raise a case with Support and request the workaround in the internal KB3227802 to disable these notifications that pop up far too frequently when engaging in conversation via the Virtual Agent or the Now Assist Panel.

View solution in original post

8 REPLIES 8

yaswanthi2
Giga Sage

Hi @Erik , It is coming from Provider>notifications -search with name as " Agentic Workflow Notification". But there is no option to deactivate this notification because it is in servicenow application

Brian Bakker
ServiceNow Employee

@Erik Nelson 

Did you raise the case? The defect "NowAssist needs your input" platform notifications appearing unexpectedly from NAP" has been raised and they are working on the fix. Unfortunately, the KE article (KB3227802) with the workaround provided in a Remote Update Set is INTERNAL. Please raise a case with Support and request the workaround in the internal KB3227802 to disable these notifications that pop up far too frequently when engaging in conversation via the Virtual Agent or the Now Assist Panel.

Thanks, Brian,

 

I've opened a case and hopefully will get a response soon.

 

Erik

Erik Nelson
Mega Sage

From Brian's post - Opening a Case is the route to go. I was provided an update set (not sure if it's release specific so not attaching here) and that this is a known defect logged in PRB2113348, which is still under investigation. Thanks, Brian!