Hello, I would suggest also doing the following additional steps within System Management workspace:
- Rebuild Full Text Entity Index
- Under Tenant more actions menu select Optimize Database
Hope that helps,
Patrick
Have you experienced the error after migration to 23R1 Branch.LocalizationCode doesn't exists in the database.
Hi @kandybeatty49,
I would suggest you check the request profiler to identify the time consuming processes. Additionally, refer the following help document for more the troubleshooting steps,
Good Luck,
Have you experienced the error after migration to 23R1 Branch.LocalizationCode doesn't exists in the database.
Hi @anahizentella94
No I have not experienced this.
The above suggestions will alleviate some of the issues, but from my experiences, the root cause would be Business events and/or Push Notifications. Acumatica has stated that using a PL screen for a business event will cause errors/issues, and if you monitor your process push notifications, it will be reflective of that.
What really pinpointed my issue was, I used the system queue monitor screen and checked out the performance issue tab for each queue type. I found where the processing time was extremely abnormal, recreated the business events/GI from scratch (do not copy or you risk just repeating the same issue), and/or simply removed unnecessary queries. My theory is that Acumatica improved/enhanced the logic for business events and push notifications without updating the legacy logic. But without us knowing what happened exactly, we just have to start from scratch so it will use the new logic.