SharePoint Throttling

Hello,

This is a long shot, as Plumsail has nothing to do with Microsoft's API request limits, but I'm looking to see if anyone has any advice on how we can fix this issue.

We are being throttled by Microsoft. It is extremely frequent, to the point in which our Plumsail HelpDesk site is almost unusable. For support agents, they run into blank screens or error messages every 5-30 minutes. This only started this week. Not much has changed since last week, except I added a couple more triggers, and maybe there is a higher influx of tickets and usage.

We have 21 triggers and 2 SLA rules that are currently active. They're generally pretty simple, but the average ticket runs around 2-5 of the triggers when it initially comes in.

Anyone have any suggestions on how we can cut down on the number of API requests we're making? This is a critical issue right now, and I've contacted Microsoft and have read this article for further insight but am still at a loss.

Thank you in advance for any help.

Hello Jake! Please ensure that you use the latest version of HelpDesk (2.1.44): it may be better optimised and thus avoid the throttling issue. If the update does not help, please load the page in incognito mode, open developer tools (F12), switch to the ‘Network’ tab, press Ctr+R, and reproduce the issue. Then export a HAR file:

Switch to the ‘Console’ tab, open the context menu of any record and save the logs:

Hello, I have dm'd you these files.

We deployed an improvement to our back end. Please ensure that you use the latest version, clear browser cache, and check whether the issue persists.

Version 2.1.45, correct? I will get back to you with the results if so.

It is continuing to happen with version 2.1.45. As of right now I don’t have a prompt to update to any newer version.

It’s not terrible and we’re not doing too much to cause this. No other sharepoint sites of ours are being throttled, it’s only this one helpdesk instance. We’ve been using Plumsail helpdesk since early 2020 and this is the first time we’ve encountered this issue. Weird. Should I send more files for diagnostic? I appreciate your help!

Yes, Jake, please share fresh browser console logs and network data (HAR) for analysis.