No Data BQM selected with today button

When is select the Today button in BQM i get a greyed out BQM with Text over saying NO DATA using historical button data shows up to date have reloaded BQM and restarted pc!!

Mine are working fine with the 'Today' button

I’ve mentioned it in the past:

https://forums.thinkbroadband.com/bqm/f/4788955-the-...

Had no explanation for it. In that thread or anywhere.

I have two BQMs graphs today with “no data” and one is fine. This is just checking now on my mobile. Go figure…

It’s definitely an artefact that’s server side. As if I click on the “Details & History” button underneath the graphs that say ‘no data’ then the graphs comes up just fine.

Sorry @seb and team TBB but it’s you and not me this time around 😅

Mm... I must have missed that one as only had this thread as unread.

Have some monitoring that detects when a graph fails to be set up, although this had some false positives where people create a graph and delete it very quickly, generating an alert to us, so it's a bit noisy.

A situation where the live graph doesn't have the data, but the historical graph for today does, is definitely some kind of issue.. Annoyingly we don't have a "login as user" function so it's harder for us to troubleshoot this. We're rolling out a change tonight hopefully which will make that feature easy to implement which lets us look into these better (without resetting users' passwords).


seb

In reply to a post by DA65:

When is select the Today button in BQM i get a greyed out BQM with Text over saying NO DATA using historical button data shows up to date have reloaded BQM and restarted pc!!

So, I see your graph on admin side so the graph has no issue being generated so there must be something up with the code that generates it somewhere.
Have you tried another web browser just in case? not just private window/retry on the same one. I'm assuming it will still happen but would be useful to know.

seb

We've found the error. The API we use throws up an 'unauthenticated' error which is what's causing that call to fail.

The change we're rolling out tonight is going to substantially change things so if this problem happens again tomorrow let us know. We don't think it's worth trying to fix this now as it's likely this won't exist tomorrow.
<fingers crossed it will be done tonight; we did try it a few weeks back and had to revert>

seb

No worries. Glad you found the cause and look forward to the update, after this evening. 🙏

In reply to a post by Pheasant:

No worries. Glad you found the cause and look forward to the update, after this evening. 🙏

Well, not as much found the cause, but know the effect. A bit like knowing there's something wrong in the engine, but we're not quite sure what. Since we're hoping to replace the engine tomorrow, it probably won't matter.

seb

Vroom, vroom 😅🏎️