Troubleshooting guides
Free, no-login guides to fix the most common Power Apps and Power Automate errors — available in English and French. Built from real-world debugging.
Power Apps
Fix the Power Apps delegation warning
The blue delegation warning means Power Apps can only process part of your data on the server. Here is what it means and how to make your formulas delegable.
Increase the Power Apps data row limit from 500 to 2000
By default Power Apps only retrieves 500 rows for non-delegable queries. Here is how to raise it to 2000 and why that is not a real fix for large tables.
Power Apps gallery shows no data — how to fix it
A gallery that stays empty is almost always a data, filter or refresh problem. Work through these checks in order.
Power Apps syntax error: semicolon vs comma
In French (and some other) regions, Power Apps uses ";" to separate function arguments and "," as the decimal separator. Mixing them up causes syntax errors.
Power Apps Patch() does not save or create the record
When Patch() silently does nothing or errors, it is almost always a schema, type or required-field mismatch. Here is how to find it.
Power Apps app loads slowly — how to speed it up
Slow start-up and laggy screens usually come from heavy OnStart, non-delegable queries and too many data calls. Here is what to fix first.
Build a responsive Power Apps screen with containers
Stop pinning controls with fixed X/Y. Use layout containers and relative sizing so screens adapt to any window or device.
Power Apps combo box / dropdown shows no items
An empty combo box or dropdown is almost always an Items source, delegation or field-name problem. Check these in order.
Power Automate
Power Automate "connection expired" / 401 Unauthorized
A 401 or "connection has expired" error means the connection the flow uses can no longer authenticate. Here is how to fix and prevent it.
Power Automate 429 "Too Many Requests" — how to fix
A 429 means your flow is hitting the connector or service throttling limits. Slow the flow down and batch your calls.
Power Automate 404 and 500 errors — how to read and fix them
A 404 means the thing you asked for was not found; a 500 means the service failed processing your request. They are diagnosed very differently.
Power Automate time zones: dates off by hours
Dates that are off by a few hours almost always mean a UTC vs local time-zone mismatch. Convert explicitly and store UTC.
Move Power Automate flows across environments cleanly
Flows break on import when connections are hard-coded. Use connection references and environment variables so the same flow runs in dev, test and prod.
Power Automate "Apply to each" is slow — how to speed it up
Loops are the usual cause of slow flows. Enable concurrency, filter before the loop, and avoid per-item API calls.
Power Platform — deployment & ALM
Complete ALM: ship Power Platform from dev to prod
The full picture of Application Lifecycle Management on Power Platform — how environments, solutions, flows and data fit together — with links to each detailed step.
Set up a dev → test → prod deployment pipeline
Promote your app safely across three environments using solutions and Power Platform Pipelines, instead of editing directly in production.
Transfer data between Power Platform environments
Solutions move the schema, not the rows. Here are the tools to move reference/config data from dev to test and prod — and what you should not move.