Hey @FAPI-8332​ ,

I didn't find anything abput this when I looked but I am not a developer. I wonder if @DarenPorter-1148​ or @TuckerBA-1087​  know why you are seeing this?

If they are busy or unable to help I will find a developer internally that can help here. Thank you for your patience!

Have a great day!

Eishi FUN

I haven't encountered these directly so I can't say for certain. My guess is that it's a defaulted future time - for example, on a DutyStatusLog that is still active, the "toDate" wouldn't have been set yet, so it might come back with a value like this.

Hey @FAPI-8332​  Sorry for the delay in getting back to you on this somehow it got lost but I did have one of our developers take a look at this. From they said it looks like something is going wrong and we would want to take a closer look at it with a support ticket. I did have a couple questions though. Is it only from one device? Many devices? Is it from only one diagnostic or many? How frequent? What percentage of records have this date?