Requests stuck in flight and unable to edit, approve, reject or delete
Summary:
We have 3 Department Disable requests that are stuck in flight, with no way to edit, approve, reject, or delete. It looks like the Department Disable requests were submitted first and in flight (dept disable requests can take a while to be fully approved), and then we had new requests entered to move those 3 depts, while the dept disables were still in flight. The Dept disable requests are now erroring out saying: The node with name 'DEPT_XXXXX' doesn't exist under parent 'PDXXX_XX'. I understand this is happening because it is trying to refer back to the parent before the
Tagged:
0