You’re offline. This is a read only version of the page.
TL;DR: If you see this error (similar for the And function), this is a spurious message that should not be displayed. The message does not affect the app runtime - it should still be working as before. To remove this message, please use this expression in the new App.OnError property to suppress it:
Share
ReportError(Filter(AllErrors, Not (": Canceled" in Message), Not IsBlank(Message)))
More details: In a recent release (version 3.21122) we made a change so that errors that are not handled by the app would start being shown to the user. The idea was to make it more explicit when bad things happen in the app. However, one of those errors that are being shown are not caused by the app itself, but by an optimization made by the platform, and should not be displayed to the user.
This is one scenario where this can happen: a label has a Text property set to the following expression:
If(
Or(
LookUp(MyTable, Name = TextInput1.Text, IsActive),
LookUp(MyOtherTable, Name = TextInput1.Text, IsActive)),
"The record is active",
"The record is inactive")
When there is a change in TextInput1, the rule will be re-evaluated, and if the LookUp can be delegated, a pair of network calls is made to retrieve the corresponding IsActive properties. If, before the call is completed, the value of the TextInput1 is changed again, the platform cancels the pending network calls (since their result would be stale), and starts new requests to retrieve the values of the IsActive property again.
When the LookUp calls are cancelled, the Or function will receive that cancellation, and it is treating it as an error (because it could not complete its calculation). The error is then bubbled up via the If function, and since it is not handled by the app, the message is shown to the user. When the network responses for the new LookUp calls arrive, the label value will be updated to what it was supposed to be, and the app continues working as it should. But the user will see the message that they shouldn't.
We are making a change to stop treating cancellation as errors (because they are not), but it will take a few weeks for the change to reach all regions. Meanwhile, we can use the new App.OnError property to "trap" those spurious cancellation errors so that they don't bubble up to the user. A way to do that is to filter the errors that are passed to it, removing those that are of this type. The expression below should take care of it:
Error(Filter(AllErrors, Not (": Canceled" in Message), Not IsBlank(Message)))
Hopefully this will help until the fix is properly deployed worldwide.
Hi even after adding im still getting the same error "Internal error in the Or function: AppMagic.Runtime.App.NamedObjectNotFoundError: The named object '150' could not be found in the runtime.." added this on app error "Error(Filter(AllErrors, Not (": Canceled" in Message), Not IsBlank(Message)))" still it persists @CarlosFigueira can you help please
Im new to all of this and just started using windows 11 home version. I downloaded several apps and i noticed that i have to click refresh several times for it to successfully pull up my page. I was using canva and was uploading images and its saying xhr internal error? Do you know if there is a solution to fix this?
@Anonymous the cancellation issue should only happen for data flow properties in controls (e.g., Text, Size, Default, FontWeight, ...) - those that are recalculated automatically when something changes, and cannot execute things that would change the state of the app (or the data), such as Patch, Collect, Update, Set, and so on. The issue you describe seems to be happening on behavior properties (e.g., OnSelect, OnChange, ...) which would not be affected by the cancellation issue that we have. If you can create a new thread (feel free to tag me so I'll be notified) with more information about your issue (such as the expression that is having the issue), we can try to solve it.
Hi @james_hathaway I have your request to the proper team to add the notification of a new version... By the way, if you have create a new feature request in the Power Apps Ideas board (or voted up one that already exists), can you send me a link to it? With that I can add a link to it to the (internal) feature request, and seeing external requests may help when deciding what to prioritize next.
Error(Filter(AllErrors, Not ": Canceled" in Message)))
The line above fixes the error for the users so it doesn't pop up everytime. But it doesn't fix the main problem using the And (&&) and Or function in the code.
We are using this for our desk reserveration app, but it keeps giving double reservations since the check whether the desk is already booked doesn't work anymore.
Any (short-term) solution on this topic?
Thank you so much for the update.
Many thanks for the Update, and the info for the "Error" workaround - very useful!
I can see that version 3.22014 has already hit a couple of the tenancies I manage, and I shall keep my eye out for the release on the other tenancies.
It would still be really nice if we were informed of a new Authoring Version when we open an App in the Studio, because as it stands, you have to remember to look at the Settings -> Support section to see if an update is available/pushed onto us.
Still, I recognise that this isn't your area (I'll try and it to the suggested new features list), and thank you for your efforts, especially for communicating with us, as it seems this is the only real channel we have for receiving useful updates!
James.
@Anonymous The fix for the 'Canceled' messages is going out with the version 3.22014. It was deployed to the Preview/First Release region last week, and this week it will start being rolled out to the rest of the world (the deployment should be completed by next week).
@james_hathaway you can also suppress the 'Error' errors by updating the OnError expression to remove errors that don't have a message. Currently if this is the case the message is being replaced with 'Error', but based on feedback we'll be changing it not do do that anymore. For now, this expression should work:
All responses (
Answers (
Error(Filter(AllErrors, Not (": Canceled" in Message), Not IsBlank(Message)))Hope this helps!
Hi @CarlosFigueira @james_hathaway ,
Any updates on this ?
Regards,
Haripriya
Stay up to date on forum activity by subscribing.
#1
stampcoin
58
#2
DS-11051211-0
20
#3
HumanOnly
6