SCTASK linked to a Change request is getting stuck in workflow and RITM not moving to Completed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-26-2023 01:24 AM
A catalog task linked to a change request when manually closed the workflow is getting stuck at catalog task stage and hence RITM is not moving to completed.
How to resolve this ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-26-2023 05:28 AM
catalog task is linked with RITM. How it's linked with Change request?
Usually the workflow will proceed once task is completed because of Wait for completion checkbox
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-08-2023 03:58 AM
Hi Ankur,
Yes the STASK is linked to an RITM that's true, but in some scenario if that task requires CAB approvals we are linking the sctask to a change request and the sctask is displayed in the related list of CR.
There are some default scripts already which works when that CR is closed related sctask also gets closed, but then again issue coming for the RITM of that sctask. Even if the sctask is closed through the CR the respective RITM is not closed and the workflow seems stuck at the catalog task level only.
I am looking for what can remove this blockage of workflow at catalog task and the close the RITM also
Here you can see below the RITM workflow is stuck at catalog task level: