Equality operator failing on Datetime objects

[vetle.huglen]

I am trying to read objects based on a timestamp referencing the beginning of an hour, as such:

The filter returns no objects, even though there are plenty of persisted objects with “Time: Start” set from exactly the same object I am using in the filter:

Are there any known bugs with floating point rounding or similar when comparing datetimes with equality operator? Or could there be underlying differences in format? This is very annoying, as I have no other convenient way of doing the filtering.

[Olav]

Hi, and thank you for reaching out!

Two questions:

• Is this action run from a shareable component?
• Have you verified that the timestamps you are comparing are exactly equal down to the millisecond?

[vetle.huglen]

1. The app is run from a service - happy to share, but unsure how?
2. Logging the datetime with .toISOString() results in the exact same datetime, down to the millisecond. I have also tried multiple methods for making sure the datetime is exactly hh:00:00.000z format, like using the built-in “go to start of hour” as well as JavaScript’s setMinutes(0, 0, 0).

[Olav]

This issue was resolved in DMs. We did not uncover any bugs with the equality operator on datetime objects.