#Screen Flow6 discussing

Hi Staci, 

This is actually expected behavior with lightning:flow when it's embedded in an Aura action override — the flow component automatically restarts itself when it hits FINISHED status unless you explicitly intercept that and close/navigate away yourself. The "Open a Page" flow action alone won't stop the restart because it doesn't control the lifecycle of the Aura component hosting it — it just navigates in a new context while the underlying flow component is still mounted and reacts to its own FINISHED status by resetting. 

The fix: handle the status change in your Aura controller, not just via a Flow action. 

1. Get the new record's Id as a Flow output 

In your Screen Flow, create an output variable (e.g., recordId, of type Text) and set it to the newly created Case's Id right after the Create Records element. 

2. Update your Aura component's onstatuschange handler 

Instead of relying solely on the flow's internal navigation action, catch the FINISHED status and manually close the action + navigate. Replace your controller's handleStatusChange function with this: 

handleStatusChange: function(component, event, helper) { 

    if (event.getParam("status") === "FINISHED") { 

        var outputVariables = event.getParam("outputVariables"); 

        var recordId; 

        for (var i = 0; i < outputVariables.length; i++) { 

            if (outputVariables[i].name === "recordId") { 

                recordId = outputVariables[i].value; 

            } 

        } 

        // Close the modal or action panel 

        $A.get("e.force:closeQuickAction").fire(); 

        // Navigate to the newly created record 

        var navEvt = $A.get("e.force:navigateToSObject"); 

        navEvt.setParams({ 

            "recordId": recordId, 

            "slideDevName": "detail" 

        }); 

        navEvt.fire(); 

    } 

} 

3. Remove or skip the "Open a Page" flow action 

Since navigation is now handled entirely in the Aura controller based on the FINISHED status, you don't need the Flow's own "Open a Page" element pointing at the record. That element was likely what caused the double behavior, since the flow tries to navigate and then restarts because the component underneath is still alive. 

The restart happens because lightning:flow treats "Finish" as "ready to run again" by default when embedded, since it is designed for cases where you want to allow re-running the same flow instance, such as a "create another case" style behavior. By explicitly firing force:closeQuickAction as soon as you detect FINISHED, you tear down the Aura component or modal entirely before it gets a chance to reset, so there is nothing left to restart. 

This pattern of catching FINISHED, closing the quick action, then navigating is the standard approach for this exact New or Edit button override plus Screen Flow plus redirect scenario.

Sure, try this.

Start with all the fields that should not be blank - street, city, country.

Then you hvae two conditions. Either there is a Country with states (province), then state should have a value. or a country without states, then you don't need a value.

AND(
    NOT(ISBLANK({!Address.street})),
    NOT(ISBLANK({!Address.city})),
    NOT(ISBLANK({!Address.country})),
    OR(
        AND(
            ISBLANK({!Address.province}),
            CASE({!Address.country},
                "Australia", 1,
                "United States", 1,
                "Mexico", 1,
                0
            ) = 0
        ),
        AND(
            NOT(ISBLANK({!Address.province})),
            CASE({!Address.country},
                "Australia", 1,
                "United States", 1,
                "Mexico", 1,
                0
            ) = 1
        )
    )
)