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]

Is the previous workflow still active?

It appears that something is still creating that approval record before the subflow is able to process. It then finds that approval and marks it no longer required. Is the previous process still available in the customer developer instance? What are the differences with this process between it and the current environment with the issue?

[Leon Tutte]

Hello Aaron,

the previous workflow is still active and available. But it doesn't include logic to interact with the new approvals. It was replaced since the workflow was static logic for certain fields and stages. But the customer needed new fields for additional internal and external approvers. And since the customer requested to be able to change and restart the approvals while the request is being worked on, the ui-macro and subflow was created.

[Aaron Duncan]

It would appear that there is a conflict between the old workflow and the macro and subflow. I would check the conditions that trigger the flow. 

[Leon Tutte]

I did that already, and the Workflow only triggers on a specific state of the request. Do you know a way to check which components have interacted with the approval record?