IoT variable update delayed

I've been using the IoT cloud to receive temperature readings without issue for about three months now, but a few days ago I noticed that the "last updated" time was a few hours late.
A brief investigation revealed that the variable continues to be updated every 10 minutes, but the IoT cloud is showing older readings. So at 3:00 the value for 12:30 will be displayed, then at 3:10 the value for 12:40 will be displayed, etc. After a few days of this the delay is approaching 5 hours.
The graph displays in the dashboard continue to show the correct values and times, down to the most recent sync.
Is this a problem with the IoT cloud, or is it something that I can fix on my end?

Brief technical details:
Using a MKR GSM 1400. The device wakes up every 10 minutes, reads the temperature, syncs, then sleeps again.
I noticed a similar problem about a month ago, though this resolved itself in only a few hours.

Hi Yandi
Are you sure? Are you looking at the live tab on the graph widget? The other tabs are delayed before update I think(?)
Also, which time are you checking? The graph c-axis is in your local time but the points are shown with UTC if you select them as in the attached (I am at UTC+10)

Hi there!
Yep, it sounds weird, but that's the case. The "live" tab doesn't display anything, but every other tab displays all the updates to the most recent. The "value" widget in the dashboard displays the same delayed value that is erroneously reported as the latest update.

I forgot to mention, but publishing an update via the API will change the value for about a second until it is somehow reset to the previous value. The graphs retain the self published updates however.

Hmm :thinking:
Do you have the variable defined as read only or as read/write?
Live should update on the chosen frequency - or is it ‘on change’? But it should update.
Are you ‘syncing’ the variable with another thing? (I have a moisture device updating the dashboard and syncing it to on Opla display. Variable setup needs care and understanding.)

It's a read only variable, but switching it around doesn't seem to accomplish much. It should be updating periodically, and it's not synching to anything else.
Mousing over the status light correctly shows the last activity, but the last update will diligently display an old value.

The historic data contains no errors as far as I can see.

Also, the "Last Update" (and value) is now about 7 hours old, so I think that time zone differences can be safely ruled out.

Hi Yandy
I am not sure if I can help you more. I don’t know if there’s a support Helpdesk from Arduino themselves? This looks like it is into the design/operation of their cloud service.
I’ll look at some of my dashboards and see if I have similar issues.

There is. You can contact them via this form:

1 Like

No worries, and thanks for trying! It's certainly got me flummoxed. I mainly posted to see if anyone had encountered a similar problem before.

I've sent off a support request, and I'll post the reply here if it solves things.


I am having the exact same problem. It has worked great for months, no code has changed. I'm also reading temperatures.

The readout of my three temperature readings are always wrong and seriously out of date. The graph is always correct and I can either wait several minutes and hope the readout will update or toggle the graphs from "1 hour" to "1 day" and back, I might be imagining it but it seems to make the readout correct itself faster.

After it finally updates, (regardless of phone app or web browser) if I refresh or force an update the values go back to being seriously out of date and the dance starts again. It hasn't been fun to see a readout of 1500 degrees and then realize it's actually only 200 because the readout is stuck in the past and refuses to update.

If I just leave the app running after it corrects itself it works great and will quickly show changes in temperature.

1 Like

Hi all, thank you for reporting the issue.. we found the root cause of the problem and fixing it.. the last values will return up to date in a few hours from now.

1 Like

It works perfectly now! Thank you very much.


Good to hear it!

The situation is back to normal since 00:20 UTC.

1 Like