Ah, this is a classic gotcha when moving catalog items from Legacy Workflow to Flow Designer — you're not doing anything wrong, and it caught me out the first time too.
The short of it: that little colored circle next to a stage is rendered by the Workflow-type field (the "stage" field on sc_req_item). The icon's appearance — orange "in progress" vs the hollow "pending" circle — is driven by the workflow context's stage state, not just the stage label. Legacy Workflow maintains that context natively as the record moves along, so you get the orange "in progress" dot. Flow Designer is a completely different execution engine and doesn't drive that same workflow-stage context, so the renderer has nothing telling it "this stage is actively in progress" and falls back to the hollow/pending style.
So the different display is expected behavior of the two engines, not a broken migration — which is also exactly why a mixed order guide (some items on Legacy WF, some on Flow) shows two different visual styles side by side. That part is the real headache for your customer, and I get why.
A few realistic options, depending on how much the visual consistency matters:
Option 1 — Standardize the engine per "visual group." Keep the items that share an order guide on the same engine so the stage rendering matches, rather than mixing Legacy WF and Flow in one guide. Not always possible, but it removes the side-by-side mismatch.
Option 2 — Stay on Flow and drive the stage from the flow. Have the flow update the "stage" field on the RITM explicitly as it progresses (Flow can set that field like any other), choosing stage values that line up with your desired progression. Caveat: because the orange icon keys off the legacy workflow context, a manually-set stage value may not reproduce the identical orange "in progress" dot — the stages will advance, but the icon styling can differ. Worth testing in sub-prod with one item before committing.
Option 3 — Move everything to Flow (the most robust long-term fix). Move everything that shares a stage display to Flow and accept Flow's rendering as the new "normal," so it's at least consistent everywhere rather than two looks competing in one guide.
I'd start by confirming all this with a quick test — drop one Flow item and one Legacy item into a throwaway order guide in sub-prod and watch the stage field. Once you've seen which engine renders what, the path forward gets a lot clearer. Happy to dig in further if you want to go the Option 2 route — let me know how the test looks.
