Unanswered

Power Automate flow slower in Production vs Sandbox environment

(0) Share

Report

Posted on by Federico_Oriani

Hi everyone,

I need your help!

I’ve built a Power Automate flow in two different Power Apps environments (one Sandbox, one Production). Both environments use a Power Apps Canvas App that triggers a Power Automate flow to perform operations on SharePoint (each environment has its own SharePoint Site – one for Sandbox, one for Production).

The issue is:

The exact same flow takes 2–3 seconds to run in Sandbox, but it takes anywhere from 3 to 10 seconds in Production, even though the Production environment has fewer data records.

Some additional context:

Both SharePoint lists have indexed columns for the fields used in the flow to speed things up.
Both flows are triggered by the Power App, have the same owner, and were recently tested heavily (but without exceeding the 600 calls per 60 seconds limit).
The logic and structure of the flow are exactly the same in both environments.
Both environments are located in the same region (Europe).

Any idea what could be causing this slower performance in Production?

Thanks in advance!
Federico

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (0)

yashag2255 24,769 Super User 2024 Season 1 on at

Like (0)

Report

@Federico_Oriani

Can you dig deeper in the flow runs of both Production and Sandbox environments and check which actions take more time to execute?

Within those actions, you can verify if there is logic or formulas that are taking longer to execute in certain cases.

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Was this reply helpful? Yes No
Federico_Oriani 60 on at

Like (0)

Report

The actions in both the Production and Sandbox flows are identical.

In the Production flow, the actions that take longer to execute appear to be random:

– In one run, it may take up to 6 seconds just to initialize a variable to empty,

– In the next run, it might take the same amount of time to execute a simple true/false condition.

So there is no clear pattern tied to the complexity of the formulas or logic within the actions. Instead, we are seeing random delays on simple actions, which do not consistently repeat across different executions.

Thank you for your response!

Was this reply helpful? Yes No
yashag2255 24,769 Super User 2024 Season 1 on at

Like (1)

Report

@Federico_Oriani

That is weird then. Generally one can expect the flows to be a little (not noticeable though) delayed in Sandbox environments compared to the Production environments.

You may have to log a Microsoft support ticket for this one.

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Was this reply helpful? Yes No
Tomac 3,966 Moderator on at

Like (0)

Report

My prod and sandbox environments both do this, actions taking several seconds longer or shorter depending on the run. My assumption is that this is due to Azure's workload at the time of execution, things may get queued and take a couple seconds longer if there are a lot of other tasks running on the platform.

Was this reply helpful? Yes No