Agentic Workflow exits after one request when using Now Assist — how to keep the workflow ongoing?

[thomasrzezn]

I’m working with AI Agentic Workflows in ServiceNow, and I have a setup with three AI Agents orchestrated together. The workflow is triggered through Now Assist (Virtual Agent promotion).

Everything runs fine for the first user request — the Orchestrator Agent identifies the correct sub-agent and runs the associated tool successfully.

However, after that one request, the workflow seems to end or exit, and the next user message starts a new session instead of continuing the same workflow context.

I want the Agentic Workflow session to persist.  So the user can have a continuous back-and-forth conversation with the same workflow instance, without restarting after each message.

Instance Version: Zurich

[warren_chan · Accepted solution]

Are you able to post the List of steps for your Agentic Workflow?

Usually a premature exit from an execution can be addressed in the instructions/prompting for the Agentic Workflow. Remember, you want your Agentic Workflow to indicate to the orchestrator when/how/how often an AI agent is executed. If your instructions/prompting is thin, then the orchestration is not going to have a lot to go on, so you will want to be very detailed and specific on this.

See these other Community posts for details:

https://www.servicenow.com/community/now-assist-articles/advanced-ai-agent-instructions-guide-servic...

https://www.servicenow.com/community/now-assist-articles/now-assist-ai-agents-prompting-guide/ta-p/3...