GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption, please take a look at our documentation.
The issue was related to the online monitor analysis pulling the whole data at once, moving the data pulling out of the loop resolves the problem.
Further the scanning range has been increased to match a wider tune able tot range. An exemplary output is shown here: