Hi, I'm querying status updates of a channel as part of my workflow. Each of these status updates comes with a "created_at" timestamp, so when I query for the last one I expect to get the latest. However, twice during March I got an status update with a "created_at" timestamp several weeks in the future, which completely messes my workflow. Because that same message always get returned as the latest for several weeks. I could code a workaround for this, but I would rather understand why this happen and how to avoid it. Attached is a CSV export from that channel, and you can see how all dates make sense and suddenly, the entry_id 502 (row 503), reports being created on March 29 2023, 20 days ahead of when it was actually created. Some background to my question: The reason why the status updates are so important in my workflow, is because I'm sending data in binary format (bitpacked) to ThingSpeak from a satellite modem (RockBlock), were a React scripts decode it and send it to another Channel for visualization. One of my encoded messages looks like "6ae5c7c895ec7803abc602c0ffffffffff07a8" To get this encoded messages, I read the status updates of the channel. Due to the way the satellite system works, in the status update I can find the IMEI of the modem, a message ID and the encoded message, therefore one status entry at the status updates feed of the channel looks like this: 300434066310190,1121,6ae5c7c895ec7803abc602c0ffffffffff07a8 So I use these status updates to retreive the binary messages.
All technical questions
View all files
