The extra "Failed update to decommissioned" task did not open for RITM000024283562

[SBhari]

Hi @Stephen Trieu (NOW),

I have did some analysis,

Let me know if you have any questions.

There are two conditions under which this task is generated:
The two conditions are as follows:
1. Pending Change Activity
Your application may not have been updated because it is associated with an open or unresolved change activity.
• Review the application for any active change controls.
• Apply the appropriate closure or cancellation.
• After completion, update the task to Closed – Completed to finalize the decommission status.

2. Underlying Infrastructure Dependencies
Your application may not have been updated because it is linked to one or more infrastructure components, such as servers or databases.
• If the server is part of shared infrastructure, remove the relationship and close the request to proceed.
• If the application is not related to shared infrastructure, close the request and resubmit it, ensuring that all underlying infrastructure is included for decommissioning.


I tested both conditions.
The second condition is working as expected. For reference, the request you mentioned was RITM000024294379, and the requests I tested were RITM000024246523 and RITM000024246522.

However, the first condition is not working as expected. For reference, the related requests are RITM000024034425 and RITM000024283562.

Can you check why only the pending change activity is not generating the task...