Approval immediately changes to "No Longer Required" after creation

[Leon Tutte]

Hello,

I have taken over a custom application for a customer which processes a separate type of request. These are submitted via a record producer on the service portal. Since the previous approvals ran through a workflow which is no longer suitable for the new approval structure, I have created a subflow for approvals which I call from a UI macro.

On my developer instance (with the incident management) the subflow works flawlessly. Also, on the customer developer instance, the flow does not report any errors during execution. Nevertheless, created approvals are set by the system from requested status (from the subflow) to No longer required right after creation.

Would anyone have any idea how I can investigate the behaviour further?

[Aaron Duncan]

You can go to the approval record itself. Look at it's history to see what account marked it as no longer needed. 

Add a comment to your subflow stating that the approval is no longer required, maybe include that it was the subflow that triggered it. Then request another approval. That will show whether the subflow is altering the approval for sure.

[Leon Tutte · Accepted solution]

For all who have the same problem. If in doubt, create a new request. In my case, the affected request was corrupted.