You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
I am storing the iothub annotations in my database with the data. To resume processing where it left of I am querying the database to get the latest enqueuedtime processed and setting this time as the startaftertime parameter. Something like the code below.
However when I run this, the last processed record is re-read from IoT Hub. I have also tried adding 1 millisecond to starttime and it still re-reads the last record. Through the process of elimination I found that adding 1930 milliseconds to starttime (iottime.getTime()+1930) is the point where the last processed record is no longer read.
var iottime = new Date(result.payload[0]["iothub-enqueuedtime"]);
var starttime = iottime.getTime();
... client.createReceiver('blah', partitionId, { 'startAfterTime': starttime }) ...
The text was updated successfully, but these errors were encountered:
I am storing the iothub annotations in my database with the data. To resume processing where it left of I am querying the database to get the latest enqueuedtime processed and setting this time as the startaftertime parameter. Something like the code below.
However when I run this, the last processed record is re-read from IoT Hub. I have also tried adding 1 millisecond to starttime and it still re-reads the last record. Through the process of elimination I found that adding 1930 milliseconds to starttime (iottime.getTime()+1930) is the point where the last processed record is no longer read.
The text was updated successfully, but these errors were encountered: