Triage and Categorize Incident does not update fields

GM5
Tera Guru

Hi All,

 

We are having issues with the Triage and Categorize incident Agentic workflow, as the subject suggest After a successful run the now assist AI provide suggestions for category and subcategory but does not update the fields it adds work notes, previously this was working.

 

After we upgraded to latest NOW assist for ITSM version this started to happen

What we did:

- Repaired plug in , did not work
- Upgraded latest version of NowAssist plug in, did not work
- Applied latest SN patch, did not work

Note: This feature is OOTB we haven't done any update.


THIS IS WHAT WE EXPECT 

GM5_1-1778682867027.png

 


THIS IS WHAT IS HAPPENING

GM5_0-1778682471049.png

**No update is done on target incident

1 ACCEPTED SOLUTION

GM5
Tera Guru

Found a solution for our scenario, it might not work for yours but could help to find what is happening, basically it was a Permission issue OOTB AI user relies on OOTB ACLs that were removed by customer.

The root cause:

Customer had several new ACLS and also disabled the OOTB  Incident* ACL (this want grants write access to all users with Itil role to table incident)  this affected the write privileges of the AI user that comes out of the box such as itsm.aia.worker

Here's what the Access analyzer showed us about Write access for  ITSM Worker ai Agent [itsm.aia.worker]  all blocked, no write access because of several ACLS customizations. bottom line this user might work if an instance is very vanilla.

GM5_0-1779813926777.png

 


Workaround / Fix:




  1. Create a new user, make sure to set the Identity type = AI GM5_1-1779814921911.png

     

  2. Add the roles accordingly to your AI agent user, mimic an integration user who already writes incidents etc.. whatever fits your ACL
  3. Test using the Access Analyzer, make sure to use the same record that helps to narrow the "what ACL permissions this AI agent might need.."
  4. Once user is done, then Go to AI agent studio and Clone the Triage and categorize ITSM incidents agentic flow
    • WHY CLONNING YOU ASK? well out of the box this AI flow cannot be edited(except for showing on now assist panel)  (see attached) so your new user with the proper access cannot be added here.
    • default data AI USER for ai agents.png
  5. Clone add a descriptive name, then add your new user under define data access section
  6. Save save save etc.
  7. Then you must do the same to each of the AI agents, not sure why but the permissions doesn't inherit from AI flow to AI agents,
    • Clone, rename and set Define data access to new AI user
  8. Once AI agents have been clonned and properly upated with new user go back to AI flow and remove the OOTB AI agents just keep your clonned copy of 
    • Link major incident or problem AI Agent (copy)
    • Categorize ITSM incident AI agent (copy)
    • Classify service and CI AI agent (copy)
  9. Save
  10. Go back to the AI agent Studio
  11. Open the OOTB triage and categorize ITSM incidents and navigate to Select channel and status
  12. In there turn off the "Engage via the now assist panl"
  13. Save
  14. This way ONLY your cloned AI flow will trigger.

**THIS WORKED FOR US

 

Can't guarantee will work for you but give it a try.

View solution in original post

7 REPLIES 7

Dr Atul G- LNG
Tera Patron

Do you mean these field changes are not showing in the activity log once updated? Are you auditing these fields?

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0723730

 

https://www.servicenow.com/community/developer-forum/how-to-make-audit-history-available-in-activity...

*************************************************************************************************************
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]

****************************************************************************************************************

Tanushree Maiti
Tera Patron

Hi @GM5 ,

 

Refer this KB : KB2989600 Agentic Workflow not working as expected when triggered from Now Assist Panel 

 

Issue

Customized version of OOB 'Triage and categorize ITSM incidents' agentic workflow sometimes gets stuck or gets something is wrong/broken in Now Assist Panel.

 

Cause

The workflow instructions in the custom version were not aligned with the latest OOB "Triage and categorize ITSM incidents"version.

The base plan lacked critical directives that the OOB includes, which is likely causing the ReActive Planner (orchestrator) to intermittently terminate the workflow before any agent or tool is executed, with the message: "Unable to proceed with incident triage because the incident description is missing and cannot be requested per the instructions."

The OOB base plan additionally includes the following directives that were missing from v2 instructions (see screenshot):
- "All three AI Agents must be executed — none should be skipped."
- "Execute all AI Agents in parallel, since there are no dependencies between them."
- "Ensure each Agent runs fully and independently, even if previous Agents complete early or produce empty results."

 

Resolution

Adding the missing directives in the instructions resolved the issue.

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

I'm sorry please don't take it personal... did you even read my post? I was clear that this is not customized, this is OOTB, people here are desperate looking for answers, we have a lot on our shoulders... at least take the time to read what we post, check the screenshots etc... If you really want to help but don't have a clear answer just don't post it has been 5 posts in a row that you post something that is completely non related to what I post.

Thanks,

Hi @GM5 

I guess before you edited your content fully and posted, I replied . My Bad.

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti