Blockers in Multimodel Assignment Creation - Nowassist Skill Kit

[YasasviU]

Multi-Method Assignment Group Prediction with Now ... - ServiceNow Community -

Hi all I am trying to develop this AI Workflow in my system. But I am facing problems near Now-Assist Workflow - where my incidents are not being read despite following the same workflow and the same coding conventions like present in this material - I am trying to build workflows and test them - but to no avail. I am getting different errors that Incident does not exist. There are other errors also - when I am creating an Retriever or an Predictive Intelligence Model, they are not working in the Now-Assist Workflow.

Can I get some help on what are the technical bugs I can face and how to fix them? Any articles to improve my understanding? And someone technical who can guide me if I am really stuck somewhere? 

I am an amateur at Servicenow AI and Agentic Workflows but I want to learn and contribute so please help me. 

[Vikram Reddy]

Hi @YasasviU,

The "Incident does not exist" error is almost certainly a glide_record input problem, not a broken workflow. Now Assist Skill Kit (NASK) allows exactly one glide_record type input per skill, and that input is only readable inside Prompts, using something like p.input.incident.short_description. It is not readable inside Tools (Script or InlineScript). If your tool script is trying to do a new GlideRecord against the record passed into the skill, that lookup will fail because the tool never actually receives the record, it only sees whatever explicit string inputs you wired to it. That mismatch is what usually surfaces as "record does not exist."

Same root cause tends to explain the Retriever and Predictive Intelligence issues too, they're each missing a separate piece of setup that has to exist before the skill can use it:

1. Record input: keep glide_record only for what you reference in the prompt directly. For anything a tool needs to query (a different table, a calculated value, group membership, etc.), pass it in as a plain string input and fetch the value explicitly in Flow Designer before calling the skill, don't rely on the skill to pull it out of the record itself.
2. Retriever: a Retriever tool just points at an existing AI Search source, it does not create one. You need an AI Search source and index already built and indexed for the incident table (or whatever you're searching) before it will show up as an option in the tool picker. If the dropdown is empty, re-index the source first, and confirm you have the sn_skill_builder.admin role, since retriever visibility is gated on that.
3. Predictive Intelligence tool: this tool type was only added in NASK v4.0.3 (Xanadu Patch 9 / Yokohama Patch 3), so check your Skill Kit version first. It also expects a model that's already created, trained, and active in Predictive Intelligence, the skill can't train one for you. If the model isn't showing up or errors on call, go check the solution's training status directly in Predictive Intelligence Workbench before touching the skill again.
4. Diagnostics: before you keep hand-testing in Flow Designer, go to Now Assist Admin > Features, find your workflow, open the skill, and use Run diagnostics if it's available. It validates the underlying capability setup and will usually point straight at which piece (input, tool, or capability definition) is misconfigured.

Honestly, the article you linked packages a lot into one build, three tools plus a nested skill plus an AI Agent Studio workflow, so it's easy to get one wiring detail wrong and have it look like everything is broken. Worth isolating: test the NASK skill standalone from the Skill Kit test panel first (check the Grounded prompt and Tools tabs in the results), and only once that's clean move on to wiring it into the AI Agent workflow. That way you know whether the bug is in the skill or in the flow/trigger around it.

Thank you,
Vikram Karety
Octigo Solutions INC