Answered

Release 3.25111.6 Caused ~370 errors in my app

(2) Share

Report

Posted on by TF-17110102-0

Last week I launched an app for my workplace that is very important. I decided to check on it today to brainstorm what all will need to be done in the following week when I was greeted with ~370 errors that had not existed last week. It is extremely important that I be able to update and work on this app.

From what I can tell from the version history, there was a small patch that went out after the last time I worked on the app, as the working version of the app has the Power Apps Release 3.25103.13.

It would appear between these two releases that the schemas of Component Actions are no longer recognizable unless initialized in a context variable or global variable. This is a big issue for my app as when running the same action ~20 times concurrently, neither of these are an option, and I am instead using With variables.

Is this intended or a mistake that will be remedied eventually?

Categories:

Building Power Apps

I have the same question (8)

All responses (4)

Answers (1)

Sort by

Suggested answer

developerAJ 4,763 on at

Like (0)

Report
Copy link

Link copied!

Please verify the schema of the Merge_Grades component property.

It appears to be expecting the schema of a different property. If you are using a global variable, it should work as expected; otherwise, you may try enabling App scope in component

Was this reply helpful? Yes No
joaocsantos 23 on at

Like (1)

Report
Copy link

Link copied!

We're experiencing the exact same issue. Our Component Actions' return values are no longer recognizable triggering dozens of schema errors across multiple apps.

Relying on global variables isn't a viable workaround here: it breaks concurrency (we're firing the same action multiple times in parallel without shared state conflicts), and it undermines the core value of Action returns for reusability. These actions are designed to be modular and portable across canvas apps and components—downgrading to globals defeats that purpose and forces major refactors.

This feels like a regression that's blocking critical updates and development. —can you confirm if this is an unintended breaking change?

Any ETA on a hotfix to restore direct schema recognition? Upvoting this thread and hoping for a swift remedy!

Example:

1 people found this reply helpful.

Was this reply helpful? Yes No
TF-17110102-0 20 on at

Like (0)

Report
Copy link

Link copied!

@developerAJ the schema for Merge_Grades is fine to the point where if I delete the custom property and recreate it, this will temporarily work. However the issue presents itself again upon reloading the app. This leads me to believe it is not an issue with the schema but how Power Apps is recognizing the schema.

The app is already in App Scope. I have stated in the question itself that Global Variables will not be viable for this problem.

Was this reply helpful? Yes No
Verified answer

TF-17110102-0 20 on at

Like (1)

Report
Copy link

Link copied!
@joaocsantos I have good news!

So I spoke with support and they did inform me that this is an error that will be resolved in the future.

They also gave me a solution that will allow development until this fix becomes available.

Once you open your app in the editor, you can paste this to the end of the URL. (Do not modify the URL in any other way besides pasting this at the end): &studio-version=v3.25103.13.349161645

Navigate to the updated URL and then you can confirm the version is updated by going to 'Settings -> Support -> Authoring Version'.

If there are still errors, this can be caused by something that happens at runtime. So just save the app and reload and this should resolve any of those errors.

After this change has been made you will need to use this modified URL to edit your app or else it will revert to the most recent Power Apps version again. So until this problem becomes resolved I recommend bookmarking the modified URL.

It is a shame that manually changing the 'Authoring Version' inside of the app only changes the version for the session and does not save/publish that version. Maybe I am missing something but this seems fairly useless and I think they should change it for when situations like this happen.

If this situation happens again in the future and you need to get the correct version number for a release you can find that information here. (Because although the version I needed to revert to was 3.25103.13 it was referred to internally as 3.25103.13.349161645): https://make.powerapps.com/canvasDebug

I apologize if they is slightly incoherent and poorly formatted but I lost more time of work than I would like to this issue and must try to catch up! Reach out to me if this doesn't work for you and I can try to help figure out why.

5 people found this reply helpful.

Was this reply helpful? Yes No