Short answer
Look up the exact message or error code, such as 429, InvalidTemplate, or InvokerConnectionOverrideFailed. For each message on this page, you'll find the cause according to Microsoft and the fix. Documented causes include too many requests in a short period, missing values (null), insufficient permissions for a connection, and blocked network requests.
Jump to: Error 429 · InvalidTemplate · Flow turned off · Try and catch · Desktop flows · Flows called from Power Apps · Network and status 0 · IfError
How to find the cause
- Power Automate: In run history, open the failed run and then the failed action. Check its available inputs and outputs. Depending on the action's settings, they may be hidden.
- Power Apps: Live monitor shows recorded requests and the available details from the monitored session, with status. For network issues, also open the Network tab in your browser's developer tools (F12).
Power Automate
"Rate limit is exceeded. Try again in 27 seconds." (error 429)
Error code 429 (Too Many Requests). 27 seconds is Microsoft's example, the wait time in your message may differ.
Cause: Every connector has its own throttling limits. If a flow calls a connector too often in a short time, for example in an "Apply to each" loop, the service responds with 429.
Fix:
- Spread calls over time, for example with less parallelism in the loop.
- Batch supported operations or filter at the source as early as possible, for example with a filter query (OData) instead of a condition for each item.
- Remove unnecessary actions from loops, and use "Select" and "Filter array" instead of loops.
- Use a different connection only where the limit is per connection.
If the action supports retries, its retry policy controls subsequent attempts. According to Microsoft, the default policy sends up to 12 retries for the Medium and High performance profiles and up to two for Low, at exponentially increasing intervals. Retries count as actions.
This is different from Power Platform request limits per 24 hours. What happens when a flow is throttled consistently is covered below under "Flow turned off".
"InvalidTemplate. Unable to process template language expressions. The provided value is of type 'Null'."
Run history shows this message in English even when the user interface is set to German. The German version of Microsoft Learn translates it as „Vorlagenspracheausdrücke können nicht verarbeitet werden. Der angegebene Wert ist vom Typ 'Null'.“
Cause: An action receives null where it expects a value of another type, for example because an optional field in the trigger isn't filled in. null isn't the same as empty text.
Fix: Handle missing values before you use them:
- with a condition that checks that the value isn't
null - with the
?operator when accessing an optional field. If the field is missing, the access returnsnullinstead of an error. - with
coalesce()and a fallback value of the expected type
The sample reads optional text from the trigger and returns empty text if the field is missing or null. You can add it in the fx editor, for example to the Inputs of a Compose action:
coalesce(triggerBody()?['Comment'], '')
You'll find more expressions in the cheat sheet for Power Automate expressions.
"Failed to Fetch", "Client Request Aborted", or "Network Error"
In the German version of Microsoft Learn, the messages read: „Fehler beim Abrufen“, „Clientanforderung abgebrochen“, or „Netzwerkfehler“.
Cause: These messages appear when you create or save flows and connections or move between pages. A company firewall or proxy can block access to a required Power Automate endpoint.
Fix: Ask your IT team to check the endpoints Microsoft lists in the "Required services" section of Limits and configuration (opens in a new tab) and allow access where needed.
Flow turned off: 90 days without a trigger or 14 days with errors
Microsoft documents these three examples of when Power Automate automatically turns off a cloud flow:
- 90 days without a trigger: A cloud flow that isn't triggered for 90 days might be turned off. Owners and co-owners are notified 30 days in advance. Flows with a premium-licensed owner or an assigned capacity license (Power Automate Process, per flow) are exempt from this rule.
- 14 days with errors: A flow whose trigger or actions fail continuously for 14 days is turned off.
- 14 days throttled: Power Automate turns off a cloud flow after 14 days of continuous throttling. If the flow is hitting platform capacity limits, assigning Power Automate Process capacity can help. For connector-specific limits, check the affected connector.
Fix: In the 14-day cases, fix the cause first and then turn the flow back on. A flow turned off for inactivity can simply be turned back on.
Handle errors: try and catch with scopes
Instead of handling each error individually, Microsoft recommends a pattern with two scopes:
- Put the main actions in a "Try" scope.
- In the "Catch" scope after it, go to Settings > Run after and select "Has failed" and "Has timed out" for "Try". Clear "Is successful".
- In the "Catch" scope, add a Filter array action and set From to
result('Try')if "Try" is the scope's internal name.result()returns the top-level actions in that scope. Filter for the statusFailedorTimedOut, for example for a notification. - If the flow should end as failed, add the Terminate action with the Failed status.
Power Automate for desktop
"Failed to get UI element" or "Failed to get window"
Cause: The desktop flow can't find an element or window that existed when it was captured. Possible reasons according to Microsoft:
- The window or element isn't visible during the run or appears too late.
- The action refers to the wrong element.
- The window title or the structure of the application changed, for example after an update.
- The application runs with admin rights, but Power Automate doesn't.
Fix:
- Use "Wait for window content" for a desktop element or "Wait for web page content" for a web element that appears later.
- Test the selector, repair it, or replace changing parts, for example with the "Starts with" operator instead of "Equal to" for the window title.
- Recapture the element after an application update.
- For attended runs, align the privileges of Power Automate and the target app. Unattended desktop flows can't run with elevated privileges.
Learn more about desktop flows on the Power Automate Desktop page.
Power Apps
"Delegation warning"
The warning means Power Apps can't pass a query entirely to the data source. The app then evaluates only the first 500 records by default. See Delegation in Power Apps for causes, checks, and fixes.
"You don't have the correct permissions to use a connection."
In the German user interface, according to Microsoft Learn: „Sie verfügen nicht über die richtigen Berechtigungen, um eine Verbindung zu verwenden.“
Cause and fix according to Microsoft:
- The app uses an older implicit connection that isn't a secure implicit connection. The app's author then converts it to a secure implicit connection.
- The app already uses a secure implicit connection. In that case, try republishing the app and test access again.
Errors when an app calls a flow
When a canvas app calls a flow, Microsoft documents different causes and fixes for each code.
Changes to flows in production: For a published app that many people use, copy the flow with Save As, change the copy, point the app to the copy, and turn off the old flow only after everyone uses the new version.
InvokerConnectionOverrideFailed
After the connection changes, the app still uses the flow's previous metadata. In Power Apps Studio, remove the flow from the app in the Power Automate pane, add it again, then save and publish the app.
MissingConnectionReference
The app expects different connection references from those in the flow. Remove and re-add the flow in the app, then save and publish.
"Connection not configured for this service."
This message belongs to MissingConnectionReference. It can happen after importing a solution if the flow metadata in the target differs from the source. In the source, remove and re-add the flow in the app, then save and publish the app. Review and back up affected customizations and data before removing unmanaged solution layers from the app and flow in the target. Removing active unmanaged customizations is irreversible and can cause data loss. Export and import the updated solution.
ConnectionAuthorizationFailed
Make sure the person adding the flow to the app can use every connection the flow references.
WorkflowTriggerIsNotEnabled
The app calls a flow that's turned off. Turn the flow on if it should be active, then test again from the app.
ResponseTimeout
The flow isn't responding within the 120-second limit for a synchronous request from the app. Check the affected run and optimize the steps before the response.
Network errors in Power Apps: status 0 in Live monitor
Cause: Status 0 means no response from the endpoint is available to the browser. Sometimes a proxy responds instead, with 403, 407, 502, or 503. Microsoft lists causes such as unstable connections (Wi-Fi, VPN, cellular), firewalls and proxies with TLS inspection, DNS filters, browser extensions such as ad blockers, and antivirus software.
Fix:
- Press F12, open the Network tab, and check the failed request, the remote address, and any proxy response. If the remote address shows only a port without an IP address, that points to a block or interruption on the device or local network.
- For comparison, test in a browser profile with extensions disabled or on another network, for example over a mobile hotspot.
- Your IT team checks the Power Platform URLs and IP ranges Microsoft documents in the proxy, firewall, and DNS filter, and TLS inspection if relevant.
Handle or suppress error messages in Power Apps
With IfError, you catch an error in a formula and show your own message with Notify. If you don't pass the error on, the default Power Apps message doesn't appear.
The sample goes in a button's OnSelect property. Orders is a connected data source with a Title text field, and txtTitle is a classic text input. Other required fields in Orders need default values. The formula returns false after showing a custom error message, or true when the record is saved. That way, both possible results have the same type.
IfError(
Patch(Orders, Defaults(Orders), {Title: txtTitle.Text}),
Notify("The order could not be saved: " & FirstError.Message, NotificationType.Error); false,
true
)
Use the App.OnError property to log errors that no formula handles or to show them with a custom notification instead of the default banner. The error functions require Formula-level error management, which is on by default in new apps. Turn it on if an older app has it turned off.
A note on separators: The sample uses a comma between arguments and a semicolon to chain actions. In a language that uses a decimal comma, such as German, separate arguments with a semicolon and chain actions with two semicolons.
Sources
- Microsoft Learn: Understand limits, error 429 (opens in a new tab) (en-us, Sep 22, 2026)
- Microsoft Learn: Limits and configuration, retry policy, 90 and 14 days (opens in a new tab) (en-us, Nov 10, 2026)
- Microsoft Learn: Limits and configuration, retry policy, 90 and 14 days (opens in a new tab) (en-us, Nov 10, 2026)
- Microsoft Learn: InvalidTemplate error due to null fields (opens in a new tab) (en-us, Aug 27, 2024)
- Microsoft Learn: Client Request Aborted or Failed to fetch error (opens in a new tab) (en-us, Jan 31, 2024)
- Microsoft Learn: Error handling in cloud flows (opens in a new tab) (en-us, Jul 11, 2025)
- Microsoft Learn: Failed to get UI element or Failed to get window (opens in a new tab) (en-us, Sep 24, 2026)
- Microsoft Learn: Common issues and resolutions for Power Apps (opens in a new tab) (en-us, Feb 26, 2026)
- Microsoft Learn: Connection errors when running flows in Power Apps (opens in a new tab) (en-us, Oct 21, 2025)
- Microsoft Learn: Troubleshoot HTTP 0 responses and other blocked calls (opens in a new tab) (en-us, Jun 5, 2026)
- Microsoft Learn: Error, IfError, IsError, IsBlankOrError functions (opens in a new tab) (en-us, Oct 16, 2024)
- Microsoft Learn: App object and OnError (opens in a new tab) (en-us, Jun 12, 2026)
- Microsoft Learn: Global support in Power Fx, separators (opens in a new tab) (en-us, Mar 22, 2024)