- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2025 06:20 PM
Hello All,
Why is the old unpublished workflow still running in old tickets instead of the new workflow? Please help.
Old unpublished workflow:
The new published workflow run too after submitting the demand:
How to completely disable or stop the old workflow that run in old demand tickets?
Anyone can give ideas? Thank you!!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2025 08:53 PM
if the old tickets have been created before the new workflow version was sent to that instancethen it will associate with the older version
That's OOTB behavior and the old tickets will run with old workflow published version
Consider ticket was created on 10th May and you deployed the new workflow version on 11th May
The workflow version on 10th is still the old one so that will get linked.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2025 08:53 PM
if the old tickets have been created before the new workflow version was sent to that instancethen it will associate with the older version
That's OOTB behavior and the old tickets will run with old workflow published version
Consider ticket was created on 10th May and you deployed the new workflow version on 11th May
The workflow version on 10th is still the old one so that will get linked.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2025 06:17 PM
Hello @Ankur Bawiskar , yes that is the OOTB behavior and for an old ticket that is running in old version of wf_context.
What we did is we canceled the old wf_context and the issue resolved.
Thanks for your response!