I am working with Azure function where cosmosdb trigger is being used to track changes against an orderId. But i am seeing azure function is picking the same changeid(logging the changeid coming from changefeed in azure function) for the same order. It is creating duplicate data in downstream.
Can anyone help us to sort this out.
The reason for invoking the same changeid for the same orderId
in below link i am seeing there might be duplicate read for "Eventual consistency" level.
While consuming the change feed in an Eventual consistency level, there could be duplicate events in-between subsequent change feed read operations (the last event of one read operation appears as the first of the next).