Power Automate - Re-Establish Connection

[ModernElectric]

Good Morning:

I have a large number of Survey123 forms created with individual Power Automate Flow(s) that automatically create a PDF printed report and emails it to selected personnel who need it. 

It has become a trend in recent months that I get a complaint from a Superintendent that they did not receive a specific report after their foreman said it was submitted. Investigating the flow(s), they fail and I have to go back in and re-set up the connection, re-establishing the webhook that is created when I build the flow. 

I need some guidance on what I need/should be doing to prevent this from continuing to happen. 

[abureaux]

Necessity is the mother of invention, after all! Trying to mitigate those exact same problems is what lead me to my current set-up.

Probably worth a new thread, but if you are reprocessing failed runs, you may wish to consider changing how your flows operate. 

For example, all my flows are two stages, with the goal of being self-sufficient and error resilient. The first stage is a quick "setup" (and relies on the ArcGIS Enterprise connectors to get my data from the FL), and the second is the "processing" stage, which could be anything from simply generating a report and sending an email, to more complex stuff like approvals, moving data between databases, running related processes, etc.

While a disruption to Esri's services still halt my processes (no way around that), once things are working again on their end, all my flows automatically process the delayed items and I can be assured that nothing is missed.

[CalvinHarmin]

I also highly kudos the methods @abureaux mentioned. 

I will add this: it is extremely helpful to include the Flow Run URL in the email you send yourself so you can one-click jump to that flow history and see what failed. The method get this URL is thankfully very simple. Just put this in a compose or variable or just plug the expression into your email action directly. 

concat('https://make.gov.powerautomate.us/environments/', workflow().tags.environmentName, '/flows/', workflow().name, '/runs/', workflow().run.name)

Replace 'https://make.gov.powerautomate.us/environments/' with whatever your own power automate domain is. 

That will be the direct URL to review that specific flow run. 

FYI this is the raw output of the workflow() expression. The concat() expression above just grabs the relevant bits to assemble the flow run URL correctly after your power automate domain. 

{

    "id": "/subscriptions/cc97105b-731d-474d-b89d-251e6750824e/resourceGroups/05B5E599E0E84C08A2129FA883E62107-75C096716CAFE86D98E4DB2EC4DC0B17-ENV/providers/Microsoft.Logic/workflows/af484700-3606-4385-8c8c-c1fe190fdf2c",

    "name": "af484700-3606-4385-8c8c-c1fe190fdf2c",

    "type": "Microsoft.Logic/workflows",

    "location": "usgovtexas",

    "tags": {

        "flowDisplayName": "test: arcgis rest API",

        "capabilities": "Premium",

        "environmentName": "75c09671-6caf-e86d-98e4-db2ec4dc0b17",

        "logicAppName": "af484700-3606-4385-8c8c-c1fe190fdf2c",

        "environmentFlowSuspensionReason": "75c09671:2D6caf:2De86d:2D98e4:2Ddb2ec4dc0b17-None",

        "state": "Enabled",

        "createdTime": "7/3/2025 6:38:25 PM",

        "lastModifiedTime": "7/24/2025 6:23:00 PM",

        "createdBy": "6e1af543-02dd-4eff-979a-c0184fa8e143",

        "triggerType": "Instant"

    },

    "run": {

        "id": "/subscriptions/cc97105b-731d-474d-b89d-251e6750824e/resourceGroups/05B5E599E0E84C08A2129FA883E62107-75C096716CAFE86D98E4DB2EC4DC0B17-ENV/providers/Microsoft.Logic/workflows/af484700-3606-4385-8c8c-c1fe190fdf2c/runs/08584482255021274964740499500CU62",

        "name": "08584482255021274964740499500CU62",

        "type": "Microsoft.Logic/workflows/runs"

    }

}

The concat() expression creates this URL:

"https://make.gov.powerautomate.us/environments/75c09671-6caf-e86d-98e4-db2ec4dc0b17/flows/af484700-3606-4385-8c8c-c1fe190fdf2c/runs/08584482255021274964740499500CU62"

[abureaux]

I actually provided that code below (under #3A), but for the general URL.

[CalvinHarmin]

Doh I see it now! You covered all the bases 😁