Power Platform Community Forum Thread Details

Hello Folks,

We are facing an issue in a Power Apps mobile offline application using a custom offline profile.

Environment:

Power Apps Mobile App
Dataverse Offline Enabled
Custom Offline Profile
Attachments/File columns used in the app

Issue:
We intermittently receive the following warning message in the mobile app:

“Network requests can fail when the app is in the background.”

Scenario:

App is configured for offline usage
Users create records with attachments/files
For Launch we used the Power automate
App may continue functioning afterward

What we tried:

Removed Concurrent()
Added Connection.Connected checks
Added IfError() handling
Sequential attachment patching instead of parallel
Reduced attachment size

Questions:

Is this warning expected behavior for Dataverse offline mobile apps?
Is there a recommended way to avoid/suppress this warning?
Are Dataverse file/attachment columns supported reliably in offline background cenarios?
Is there a way to identify which specific request is causing this warning in offline mobile apps?

Any guidance would be appreciated.

PowerAppsError.png

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Microsoft Dataverse with Power Apps

Hello CU12050758-0 ,

Yes, this warning is generally expected in Power Apps Mobile when a network-dependent operation is triggered while the app is backgrounded. Even in Dataverse offline-enabled apps, attachment/file uploads often require network activity and may not behave the same as standard offline data synchronization.

A few points:

The message itself is a platform-level warning and cannot be suppressed by app formulas.
File and attachment columns can be more sensitive in offline/background scenarios than standard Dataverse records, especially during upload/sync operations.
If the warning appears intermittently, it is likely tied to a specific network request (attachment upload, Power Automate call, connector call, or sync operation) occurring when the app transitions to the background.
Concurrent(), Connection.Connected, and IfError() improvements help with app logic, but they do not prevent OS-level background execution limits.
To identify the source, review:
- Power Apps Monitor (while reproducing the issue)
- Mobile device logs
- Dataverse offline sync logs
- Any Power Automate flows triggered during launch or save operations

The key question is whether users experience actual data loss or failed attachment uploads, or if this is only a warning message. If uploads are failing, reviewing the offline profile configuration and attachment/file synchronization behavior would be the next step.