Flow stage approval rejections not showing correctly

[Biddaum]

So in my flow I have a "ask for approval" step, that goes to our IT Security team, it is set to "anyone approves or rejects", and directly before have a stage "IT Security approval" and it uses the standard approval stages

So the issue is, when the approval request is Rejected, the stage shows on the users ticket as Approved:

Does anyone know how I can get it to actually show as Rejected?

[musislam]

HI @Biddaum 

Okay, I understand. You've shared a screenshot of the "IT Security Approval" stage configuration in Flow Designer, showing the customized state labels. Let's use this new information to refine the solution.

Problem Reaffirmed:

The image confirms that you have:

Customized the state labels to be user-friendly (e.g., "Completed" is labeled "Approved," "Error" is labeled "Rejected").
Selected the "Customized state label" option.
However, even with these custom labels, when an approval request is rejected in the preceding "Ask for Approval" action, the "IT Security Approval" stage still displays as "Approved" on the user's ticket, which is incorrect.

Solution, Focused on Customized State Labels:

The core issue remains: Flow Designer's stage display logic is likely relying on internal state values rather than your custom labels when updating the displayed stage status.

Since you are using "Customized state labels," here's how we can address this:

Identify Internal State Values:

Default States: If possible, temporarily switch back to "Use default states" in the stage properties. Note down the default labels that appear for each state (e.g., "Pending," "In Progress," "Completed," "Error," or similar). These are likely the internal values used by Flow Designer.
Approval States: If you switch to "Use approval states" it will show the state labels.

Map Custom Labels to Internal Values:

Create a mapping between your custom labels and the corresponding internal state values you identified.

If you like this opinion and your problem is resolved after reviewing and applying it. Please kindly mark this your best answer‌🌠‌ OR  mark it  Helpful ‌⛑‌ if you think that you get some insight from this content relevant to your problem and help me to contribute more to this community

[Biddaum]

@musislam thank you for replying, but you have wrongly assumed that I'm using "Customized state labels" that is just the standard heading that always shows on that form - the only customized component is the stage name of "IT Security approval".

The states in that stage are OOTB states that simply get applied when you select the "Use approval states" option on the form:

Therefore, there shouldn't be a need to map anything

[musislam]

HI @Biddaum 

is your flow chart is like below ---Task: Ask for Approval

Assigned to: IT Security Team
Approval Rule: Any member of the IT Security Team can approve or reject the request.

Flow:

If Approved: User: IT Security Team, Approval Rule: Anyone Approves or Rejects)
Continue Flow: The process proceeds to the next stage. The state does not need to be explicitly set to 3 at this point.
If Rejected:
Lookup Approval Comments: The comments from the approval record are retrieved.
Update Record (RITM record):
State: 4 (Closed Incomplete)
Comments: Optionally, the comments from the approval record can be added to the RITM record, along with any other relevant information.
End Flow: The process ends.

let me know , if its the thing or share the flow chart so I can analyze it in proper way

A small request from my end, If you like this opinion and your problem is resolved after reviewing and applying it. Please kindly mark this your best answer‌🌠‌ OR  mark it  Helpful ‌⛑‌ if you think that you get some insight from this content relevant to your problem and help me to contribute more to this community

[Biddaum]

This is the entire flow: