Patch 10.3.1 – Big Lag Fix
Major Browser Lag Fix – Notifications went Crazy
Reports had come in that TLD was “Slow” but we didn’t see anything wrong with Dialers or Servers.
Reports came in that Firefox was faster that Chrome, and so was Incognito Tabs, but then over time Firefox was slower than Chrome. This led us to look at anything part of TLD touching Session or Browser Storage.
We investigated the main TLD Front end app and noticed that for users with lots of notifications or interacting with the notifications menu ( open / close ), including on Page load once the menu was opened at least once, was duplicating the amount of locally stored notificaitons ( though not displaying the dupes ). As a day goes on this becomes a very very heavy write operation, which happens on Page Load (when lead comes in) and other times as well.
This bug was introduced last week with the addition of the Jobs System described below. It has been fixed along with two other items.
- New Notificaitons should now properly “Popup” on your screen, apparently we removed this a while ago and the notification flow was wrong.
- Notifications now again support Desktop Notifications to popup if you have allowed notifications for TLD on your browser.
Jobs System
Jobs is a re-usable set of logic, patterns and systems to allow us to add background processes that take a long time (Mostly Mass Edit) and keep track of them, cancel them, prevent duplicates, etc.
When a Job is Queued your Notificaiton Menu will open with the initial start notif as well as a progressive counter that will give you an ETA and duration of the process. You can just close the Notification Menu if you like.
You can press X in the Counting Notification and it will cancel the job. Be careful not to touch it unless intended.
Job logs can be found in Logs -> Jobs
Other Changes
- In an Effort to leave Localstorage alone even more so, we have disabled the front-end TLDialer Debug Logger as well generally don’t use this data anyways.
- We’ve Removed the 10k limit from Egress API as it made very little sense to allow for Limit 0 (Unlimited) but then limit pagination itself when trying to pull data sanely.
Thanks again all for the reports and the examples so we could track this down pretty quickly.
If you are still experiencing issues, Please Clear your Cache and Cookies and try logging in again it should put you back in a clean state (although simply opening and closing the notification menu will do this now too)