You’re offline. This is a read only version of the page.
60
Good morning,
Several users have reported that they are getting the generic "An unexpected client error has occurred" error message when performing various tasks within FO, but always triggered when clicking a menu item. It is not replicatable, and only seems to occur when the menu item is used for the first time and then not on subsequent uses.
Examples of this include posting a journal, adding a new customer, clicking to view a list of all Sales Orders etc. The timestamp within the error message corresponds to an error in the Activity Log in LCS:
ResizeObserver loop limit exceeded (0:0:/?cmp=REL&mi=CustFreeInvoiceListPage)
This is a react.js error (and searches for it report it as benign), but is returned as a response to FO, so triggers the error and interrupts the user.
It does not appear to happen when using Edge.
I have logged with Microsoft, but in the interim, can anyone suggest a way of repressing this error?
Thanks
Hi Phil,
Thanks for the update. There is no option from me to help you as, like you, I haven't encountered this issue. I do trust Microsoft Support would be able to help finding the culprit.
Thank you Judy, I already have a ticket open with Microsoft, but we are currently trying the "generic" options like running Chrome in Incognito mode, clearing user data, and disabling all extensions.
Andre Arnaud de Calavon , it doesn't seem to be linked to a particular version of Chrome - we've seen it in several versions across multiple environments.
I am not able to replicate the issue myself in Chrome, so the logical assumption is that it is related to an extension, policy, or similar at the customer with the issue.
Hi sir,
Because of this issue need more professional investigate, I suggest you create a support ticket for professional assistance following the below procedure.
admin.powerplatform.microsoft.com/support
Best Regards,
Hi Phil,
When did this behavior start? Was there an update of Chrome or the application version?
Anyway, I woud await a reply from Microsoft Support. I'm not using Chrome that much and haven't encountered this issue myself. In the meantime, Edge seems to be the solution for now.
#1
Martin Dráb
510
Most Valuable Professional
#2
Saalim Ansari
315
#3
Adis
312
Super User 2025 Season 1
Share
Report
All responses (
Answers (
