Chg flow is working as per the flows but in prod it is not working re trigger for approval and dupl

[bshivakumar]

I changed the condition status in the flow and tested it. after changing that the approvals are not getting triggered as per the conditions set.
In the Dev environment, I recreated the scenario by creating a new change with the same services, assignment group, and assigned user. As per the story:

Story point: After approval in the Assess state, the ticket should move to the Authorize state and wait for CAB approval. But instead, it was staying in the Assess state and triggering approval again.
However, in my testing, the flow is working correctly:
• New → Assess → Authorize
• Approvals are triggering properly
• No re-triggering issue
• No duplicate approvers
I also checked in the Test environment and found the same behavior. But I did not change any flows there.

[Dr Atul G- LNG]

Hi @bshivakumar 

It looks like there is a flow that is triggering this step. Please check the out-of-the-box (OOB) flow or the approval policy where it might have been overridden or modified.

[Tanushree Maiti]

Hi @bshivakumar 

.

A. Check KB (Compare and Validate 2 instances) : KB2803489 Change model state transition blocked after workflow approval 

Resolution

To complete these steps, you must have the change_admin or admin role. 

1. Go to All > Change > Administration > Change Models. Open the custom change model and locate the Assess state in the Model States related list.
2. Select New to create a state transition from Assess to Scheduled.
3. In the To field, enter Scheduled, select the Automatic transition check box, and select Submit. 
4. Review any other expected workflow-driven transitions (for example, Scheduled to Implement) and confirm they are defined in the change model. To add any missing transitions, repeat steps 1-3.
5. Save the changes to the custom change model.
6. Test with a new change request to verify the state transition completes successfully.

B. Check Flow Designer or Workflows

c. Use the Apply Change Approval Policy flow action 

d. Same situation we faced once where 2 BR was conflicting, once we corrected , it works fine.