we have finical account with investment record type. we have quick action button call "create service catalog request " this button call flow.
expected sloution; click on action then the flow calls and check record that have any existing service catalog request with draft request status , if it is true show the error msg like edit the draft and use.
false-check the flow type and create the service catalog request , show the toast notifaction and action open that new created request.
actual solution : the service catalog request is toast msg is coming but the "your flow finished" msg is poping up and need manual closing and not opening the service catalog request .
this working other envirments (sandboxs)only faiing after the winter27 realese
#Financial Services Cloud #Salesforce Developer #Flow #Quick Actions #Salesforce Admin
Hi Eeswarini,
Since this worked before Winter '27 in the same design, this looks like a genuine regression in how the flow's finish behavior is being handled after the release — not a logic error in your flow.
Background: "YOUR FLOW FINISHED" appears whenever a flow ends without a screen as its last executed element. If your flow's last step is an action (like ShowToast) rather than a screen, Salesforce falls back to this default finish screen. If this wasn't happening before Winter '27 with the exact same flow, something changed in how the platform determines "last executed element" or how quick-action-launched flows auto-close.
Fixes to try:
1. Add a final Screen element at the very end (after ShowToast), with header and footer removed, and use a Navigation-type action (e.g., NavigateToNext or similar Unofficial SF flow action) to auto-continue/close instead of a real screen the user sees. This is the standard workaround regardless of the regression, since it forces flow completion via a screen node rather than relying on default finish behavior.
2. Check the Quick Action's flow settings on the record page — Winter '27 changed some Flow/Quick Action finish-behavior defaults; confirm "Reload page after finishing" or the flow's finish handler config still matches your prior sandbox setup.
3. Compare flow versions/metadata between the working sandbox and the affected environment — if this environment got the Winter '27 upgrade first, check if a newer flow runtime setting differs.
Given it's release-tied and reproducible, I'd also open a case referencing "screen flow finish behavior change post-Winter '27" — if this is a genuine platform regression, Salesforce needs it logged to fix it broadly, not just worked around per-flow.
Reference:
https://unofficialsf.com/navigate-everywhere-flow-action/