Unanswered

Performance Issues with Co-Authoring in Power Apps Canvas Application Description

(1) Share

Report

Posted on by Ajmal1997

Hello everyone,

I am experiencing significant performance issues with a Power Apps canvas application that I have developed. The application has more than 20 screens, and we recently enabled the co-authoring feature. However, when trying to edit the application, it takes an excessively long time to load. Additionally, I frequently encounter the following error message:

“Can’t connect. Can’t establish a reliable connection to Power Apps. This could be a temporary problem or a problem with your network.”

Details:

App Complexity: The application consists of over 20 screens.
Co-Authoring: Enabled the new co-authoring functionality.
Error Message: Frequently see the “Can’t connect” error message.
Network: Checked and confirmed that the network connection is stable.
Steps Taken:
Optimized data loading by reducing the number of columns retrieved.
Minimized the number of data calls and calculations in the OnStart property.
Ensured the network connection is stable and has sufficient bandwidth.
Used the Concurrent function to load data faster.
Despite these efforts, the performance issues persist. I suspect that the co-authoring feature, which is currently in preview, might be contributing to these problems.

Request:

Has anyone else experienced similar issues with the co-authoring feature in Power Apps? Any suggestions or workarounds would be greatly appreciated. Additionally, if there are any known limitations or best practices for using co-authoring in complex applications, please share.

Thank you!

Categories:

Experimental features

I have the same question (0)

All responses (2)

Answers (0)

Sidhant_02 986 on at

Like (0)

Report
Copy link

Link copied!

Hi @Ajmal1997,
Even I encountered a similar issue and with the new update I thought it might have been resolved, previously there was a Git Repository that was been used (in Co-Authoring) but now they have made slight modifications to it. So, what I have observed when the Co-Authoring feature is enabled when two developers are working on did not find any issues but the moment when more than 2 developers/users start working it causes few issues like loading time, some of the changes get missing, etc.

So would like to know from the community how is the parallel development been done in the industry right now we need to create a copy and make changes which we did before Co-authoring to avoid any changes being lost.

Regards,
Sidhant.

Was this reply helpful? Yes No
AA-20091029-0 2 on at

Like (0)

Report
Copy link

Link copied!

Hi @Ajmal1997,

I've run into a similar issue and was hoping the recent update would resolve it. Previously, the Co-Authoring feature used a Git repository, but it seems they've made some modifications. Here's what I've observed: when only two developers are working simultaneously, things go smoothly. However, once more than two developers are involved, several issues start appearing.

For example, changes made on one screen by a developer sometimes show up on different screens, and components created on Screen A might disappear and unexpectedly appear on other screens. Additionally, the entire Canvas Studio often becomes unresponsive, adding to the frustration.

I'm curious how others in the industry are handling parallel development. Right now, we're falling back on the old approach of creating separate copies to avoid losing changes, just like we did before Co-Authoring was introduced.

Regards,
Akshat

Was this reply helpful? Yes No