Power Apps makers and admins run into a recurring set of problems across connectors, Power Automate integration, Power Fx, Studio, and platform behavior on specific devices. Microsoft maintains a consolidated troubleshooting reference for these issues, and this article walks through each one case by case, so you can match your symptom to the right fix instead of searching from scratch.
Before diagnosing a specific problem, it is worth reviewing Microsoft’s general troubleshooting strategy guidance, which covers how to isolate whether an issue is functional or performance related. That framing helps you decide which section below actually applies to what you are seeing.
Connectors and delegation
Connector and delegation problems are usually the first thing makers hit once an app moves past a trivial data source. Delegation limits and connection permissions behave differently depending on the connector type, so the fixes below are grouped by the specific symptom rather than a single blanket explanation.
Issue: You do not have the correct permissions to use a connection
This message shows up in two distinct scenarios, and the fix depends on which one applies.
Resolution: If the app shares an implicit connection that is not a secure implicit connection, share the connection directly with the end user. This is a workaround rather than a long term fix. The author should convert all connections to secure implicit connections instead. If the app already uses a secure implicit connection, republishing the app is often enough to resolve the problem.
Issue: Automatic next links do not work in galleries or grids for action-based connectors
Resolution: This is expected behavior, not a bug. Action-based connectors do not support next links, which are the properties on query results that let a gallery or grid automatically load the next page of data. If your data source is action-based, plan pagination logic manually rather than relying on automatic next links.
Issue: SQL data sources no longer add a [dbo] prefix to the data source name
Resolution: This reflects a platform change to how SQL Server connections are named rather than an error condition. Update any formulas or references that assumed the older [dbo] prefixed naming convention, and confirm current naming behavior against the SQL Server connector documentation before you troubleshoot further.
Issue: Custom connectors break after moving a Dataverse-backed app
This affects apps built with Power Apps version 2.0.540 or earlier that rely on a Dataverse database and use at least one custom connector from a separate environment. Without a fix, users see a dialog stating the API was not found.
Resolution: Deploy the custom connector to the same environment as the Dataverse database, then update the app to reference the newly deployed connector. Treat this as an environment strategy item: apps and their custom connectors should live in the same environment to avoid this class of failure entirely.
Issue: Column names with spaces cause formula errors
Resolution: If you are working with a list from Microsoft Lists, a SharePoint library, or an Excel table where a column name contains a space, wrap the column name in single quotes, for example someList.’Color Tag’.
Issue: Blank sign-in dialog when sharing apps connected to on-premises SharePoint
When an app relies on connections that are not automatically shared, such as an on-premises SharePoint site, users opening the app in a browser see a dialog box with no visible text after selecting Sign in.
Resolution: Select or tap the close icon in the upper right corner to dismiss the dialog. Note that this does not occur in Power Apps Studio or Power Apps mobile, only in the browser experience, so this is useful context when setting expectations with end users.
Issue: Only the first 500 records of a data source are accessible
Resolution: This is the delegation limit, not a bug. Power Apps delegates supported operations to the data source, but for operations that cannot be delegated, it warns at authoring time and works against only the first 500 records. Review which functions are delegable for your specific data source and restructure formulas to stay within delegable operations wherever possible.
Issue: Excel or SharePoint Lists behave unexpectedly as data sources
Resolution: Excel data must be formatted as a table before it can be reliably used as a data source; unformatted ranges are not supported. Separately, Microsoft Lists is supported as a data source, but SharePoint libraries, certain list column types, and columns supporting multiple values or selections are not. Confirm your source data meets these structural requirements before building against it.
Issue: Sign-in failures on certain Android devices using an authenticator
Resolution: This is caused by an OEM-imposed limitation on certain devices rather than a Power Apps defect. If users hit authenticator sign-in failures, check the device manufacturer’s known issues for the ADAL broker authenticator not responding error before escalating further.
Issue: Apps cannot save null or blank values to data sources
Resolution: Check whether the Formula-level error management feature is disabled under Settings, Updates, Retired. Enabling this feature resolves the inability to save null or blank values.
Power Automate integration
Issue: Power Automate flows become orphaned in Power Apps
Resolution: Flows added through an older version of the Power Apps panel can become orphaned and removed. Re-add the affected flows manually to restore functionality.
Issue: Custom page flow metadata falls out of sync in a model-driven app
This happens when a Power Automate flow embedded in a model-driven app custom page is updated after embedding, leaving the custom page referencing stale metadata.
Resolution: For each embedded flow, edit the custom page that uses it, open the Power Automate pane and refresh the flow, then save and republish the custom page. After all affected pages are updated, edit the model-driven app, make a minor change to trigger the save option, and save and publish the app.
Power Fx
Issue: Connection.Connected returns the wrong value during OnStart in Power Apps for Windows
While offline, the Connection.Connected formula can incorrectly return true immediately after the app starts in Power Apps for Windows.
Resolution: Use a Timer control to delay execution of any logic that depends on Connection.Connected, giving the platform time to report the correct connectivity state before your logic runs.
Issue: Date and time values behave inconsistently
Resolution: Date and time issues are common enough to warrant their own dedicated references. Consult Microsoft’s canvas app date time troubleshooting guide and the model-driven app date time troubleshooting guide depending on which app type you are working with.
Regional performance
Issue: Power Apps Studio takes more than 30 seconds to load in China
Resolution: This is a known regional performance characteristic rather than a fixable configuration error on the maker’s end. It does not affect tenants hosted locally by 21Vianet, so tenant hosting location is the relevant variable to check if you are seeing this symptom.
Power Apps Studio and forms
Issue: Trouble accessing or starting Power Apps
Resolution: Startup and sign-in problems are covered separately in Microsoft’s dedicated startup and sign-in troubleshooting article. Use that reference before assuming the problem is Studio-specific.
Issue: Cannot change dimensions or orientation of SharePoint forms
Resolution: Use the Custom size setting as a workaround. Reset the setting by selecting Small size, toggle Orientation to Portrait and back to Landscape, then select Custom and enter the desired screen size. For reference, the Small Portrait preset is 270 by 480, and the Small Landscape preset is 720 by 480.
Issue: Cannot copy and paste screens across apps
Resolution: Direct screen copy-paste across apps is not supported. Instead, add a new screen to the target app, copy the individual controls from the source screen, and paste those controls into the new screen in the target app.
Issue: Multiple errors appear when changing SharePoint form layout from Portrait to Landscape
This happens when customizing SharePoint forms in certain languages, where switching from the default Portrait layout to Landscape produces yellow triangle errors across controls.
Resolution: Select Undo to clear the errors while retaining the Landscape layout.
Issue: Changing a flow in a shared app does not take effect
Resolution: Modifying a flow after the app has been shared, such as adding a service or changing a connection, requires more than editing the flow in place. Remove the flow from the shared app first, re-add the updated flow, and then re-share the app.
Issue: Cannot change a Title field referenced by lookups
Resolution: If another table references the Title field through one or more lookups, changing that field directly causes a save error. Remove any lookups to the table, change the Title field, and then re-create the lookups afterward.
Issue: Sorting and searching fields are not configured on apps generated from data
Resolution: When Power Apps generates an app from data, the field used for sorting and searching is not automatically set. Edit the Items formula for the gallery to configure the correct field.
Issue: A newly shared app is not immediately usable
Resolution: This is typically a propagation delay rather than a permissions or configuration problem. Wait a few moments and the app should become available.
Issue: Cannot change data using a custom card in the Form control
The stock custom card is missing the Update property, which is required to write changes back to the data source.
Resolution: Select the Form control, insert a card from the right-hand pane based on the field you want the card to show, unlock the card, and then remove or rearrange the controls inside it as needed.
Issue: Card gallery is deprecated
Resolution: Existing apps using card galleries continue to run, but new card galleries cannot be added. Replace card galleries with the newer Edit form and Display form controls going forward.
Browser performance
Issue: Browser runs out of memory while using Power Apps
Resolution: This typically occurs with the 32-bit version of Google Chrome or Microsoft Edge. Switch to the 64-bit version of the browser to resolve the memory ceiling.
Power Apps for Windows
Issue: The Windows mobile app does not support the Dropbox connector
Users see a dialog stating the service cannot be reached and to check the network connection or try again later, even though the underlying problem is a platform limitation rather than connectivity.
Resolution: Use a web player on the Windows platform instead of the Windows mobile app when the Dropbox connector is required.
Issue: Microsoft Entra Conditional Access with device compliance requirement blocks sign-in
When Conditional Access is set to require the device be marked as compliant, users receive a sign-in error stating the application contains sensitive information and can only be accessed from devices or client applications that meet enterprise management compliance policy.
Resolution: Use a browser to access Power Apps instead of the Windows application, since Conditional Access enforcement in this scenario currently does not work with the Power Apps for Windows client.
When your issue is not covered here
If a problem you are facing is not addressed above, search Microsoft’s broader Power Apps support resources or contact Microsoft support directly through the Power Platform admin center. Building this kind of troubleshooting reference into your own team’s onboarding material, alongside your environment and ALM documentation, reduces the number of support tickets that never needed to leave the team in the first place.
Source: Microsoft Learn, Common Issues and Resolutions for Power Apps, last updated February 26, 2026.