Closed scale-tone closed 3 years ago
Just so I'm not making assumptions, where are you getting these values from?
That's what DurableOrchestrationStatus.History
contains, returned by DurableClient.GetStatusAsync(instanceId, true, true, true)
.
Just following up on this - sorry for the long delay. Do you remember if your MSSQL instance was on the same box or a remote box/container/service? That's one potential explanation since in some cases the timestamp comes from the local machine and in other cases it might come from the SQL Server instance. I'm otherwise not sure why you'd see this and would need to do a deeper investigation.
Database was (still is) in Azure, the rest was running on my laptop. So yes, this would explain that.
I'm observing this:
Everything was run on my devbox, aka on the same computing instance, so this cannot be explained as clock difference. Is that normal?