• Guest - w'd love to know what you think about the forum! Take the 2025 Survey »

New Libre warning

jaywak

Well-Known Member
Messages
947
Location
Norwich
Type of diabetes
Type 1
Treatment type
Insulin
Dislikes
Cold weather, angry people, queues,
I've only just started getting this message on my phone , glucose reading paused your sensor runs continuous quality checks and glucose readings have been paused once it passes these checks your sensor will resume providing readings please check again in ten minutes . I have never seen it before but it's done it about six times with the latest sensor and it lasts a lot longer than ten minutes , is this something new ?
 
T2 self funding Libre 2+
I haven't seen this message so far.
Using an Android phone.
I have seen messages saying sensor error, of scan error please try again in 10 minutes.
Are you looking at the error log or seeing the message directly on the screen?
 
Directly on the screen , I've had the sensor error many times before but never had the quality check before .if it's doing a quality check I wonder why so many times in such a short time ,the sensor is only five days old .
 
Another type 2 self funding the Libre 2 plus, I haven’t seen the quality check notification (yet!) either.
 
I haven't seen it but I read a post by someone on Facebook about two of their sensors doing this before a sensor error - replace sensor message appeared.
I hope your sensor will resume working as normal again!
 
I wonder if they are now splitting out the messages that would previously have been lumped under sensor error.

What does the log show? Is there a specific (err) code which occurs when these messages are being displayed?
 
I sometimes have errors in the libre app that are not repeated in other sensor scanning applications. Try installing diabox or juggluco
 
I just checked into event log and it actually shows exactly what it shows on the screen but very oddly it has recorded it every minute since I fitted the sensor five days ago . I don't know if it's an error code but the number 373 is also there .
 
I think they have changed the wording on the error which used to just say something like "Glucose reading is unavailable. Try scanning again in 10 minutes."
 
i have also had this message pop up for the first time (on Android App). I was abroad on holiday (in the heat) last week, and thought it might have been overheating of the sensor. It repeated the message 2 more times before then returning to normal readings. Overall it didnt provide readings for about 20-30 minutes
 
I guess it must just be something new they have added recently but I don't think the wording of the message is correct though , if it was a quality check surely it would only happen once or twice in the fifteen day life of the sensor and only last the said ten minutes , I have emailed abbott and asked them to explain , I'll get back to you and let you know if they reply .
 
I see these messages (or rather what we assume is the previous name - sensor error wait 10min type message) quite a lot, but then I have lots of troubles with calibration of the sensors. They often happen when there's a fast transient change in BG, which makes sense - the sensor wants to stop giving you a value which may be based on a hardware failure.

Presumably once it sees that the rate of change has reduced to be within some allowed boundaries it starts producing data again (often with a different calibration I also find)
 
I have had the pause 10 min message on mine too. There are several messages that can pop up. A week or so a go I was out doing my exercise, as my blood sugars were high, when I suddenly felt like I wanted to throw up. I felt horribly nauseas. I checked my Libre. There was a message box which said something like 'on pause while blood readings stabilize' or something like that. I hadn't seen that message before. I thought my blood sugars were more likely going down than up, luckily I had some sweet candy in my pocket, so I ate one. I was only about a 5 min or so walk from home. I got in, my Libre was still on pause so I finger pricked and I had a reading of 3.2. That was after I had eaten candy. My Libre kicked back in around 2.5 if I recall.
 
Abbot did reply with a form to fill in I think for a replacement sensor and a question if I was either using a Libre 3 or other so I ticked other and it then gave me a tel no to ring so as the sensor is now working fine I did not bother , so as they didn't answer my query I am none the wiser .
 
Hi,

From experience & from what I know.
If the readings from the sensor are erratic. The readings can hold fire untill the sensor can chop sense into what’s going on?
Usually rapid jumps interstitial readings??

I’ve had the sensor is too hot & give it 10 like I’m just about to use a toilet after someone else…
Sometimes there is a dropout period on the graph too, which cannot be scanned in..But only for 10 or 20 minutes..

@jaywak . One thought comes to mind.
Are you suitably hydrated with the heat?
From what I’ve read hydration could affect interstice fluid..
 
Zhnyaka said:
I sometimes have errors in the libre app that are not repeated in other sensor scanning applications. Try installing diabox or juggluco
Click to expand...
Some sensor issues or warning notifications like the one highlighted in this topic can still affect Diabox or Juggluco.
They just don’t send the feedback the official Abbott app does..

Having said that, they do work fantastically for a heads up reading on the home screen or Lock Screen along with certain smart watches..
 
I started getting these messages for the first time with my last sensor and now with this one too. It seems to happen when my blood sugar is rising rapidly or falling rapidly and it will go offline for about 30 minutes which isn’t great if it’s falling rapidly. Looking at the event log I can’t see this message a lot. I thought maybe there was an app update. Sensor di work all the way to the end though.
 
I've also started getting this new error message a lot since the latest update, and it's really annoying. I used to get the reading unavailable thing maybe once or twice during the lifetime of a sensor before, but now it's happening many times a day, like they've massively reduced the threshold for it.

I understand that they want to avoid responsibility for people acting on incorrect information, but to completely stop giving any readings at all for extended periods whenever BG changes slightly faster rather defeats the whole purpose of wearing it in the first place. Why not just keep giving the readings, but with a warning they may be unreliable? Also how have they *still* not added status bar/lock screen readings to the app?

It may be time to switch back to using one of the unofficial apps.
 
You must log in or register to reply here.
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn More.…