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:
Error(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.
