Using "Add Stage" feaure in Flow Designer doesn't let me choose an existing stage

[Danny Barker]

Hello,  I have created several Request flows in Flow Designer and have been using the "Add Stage" tool so that we can take advantage of the progress from a list view.  When setting up a few notifications, I need these to send based on the stage.  The problem I see is that I now have so many duplicates of stages from all the recent flows and using the "Add Stage" feature.  I created a test flow to see if I just missed that option to use existing stages but I only have the option to create more.  Is there a way to select existing stages from this tool or should I just be updating the stage from Update Record?  Is this the expected behavior when you have multiple flows using "Add Stage".  Thinking maybe to send notification based on State as well since so many duplicate stages are shown. Any tips or thoughts on this would be greatly appreciated.

[dora745nevels]

It is expected behavior for Flow Designer’s Add Stage tool to create flow-specific stages, which often leads to the clutter and duplicates you’re seeing in the choice list. To regain control, you should avoid "Add Stage" and instead use the Update Record action to manually set the Stage field. This allows you to pick from your existing, global Stage choices (defined on the sc_req_item table) rather than creating new ones. If your workflow logic is becoming too complex with stages, triggering notifications based on the State field is a much cleaner, more standard approach, as States are generally more stable and less prone to duplication than Stages.