I know this topic is old, but as of today, this solution isn’t working for me. For some reason, a freshly created item with the same creation and modified dates is showing using the above logic. Essentially, the condition “parent group’s thing’s creation date < parent group’s thing’s modified date” is evaluating to true, even though they are the same date.
I was able to get something working using the following:
“Parent group’s thing’s modified date change seconds to 0 > parent group’s thing’s creation date”
but this is limited in that if the item is modified in the same minute that it is created, it will not show.
This new behavior seems like a bug to me, and suggests one of two issues:
- The “<” check is actually a “<=” check behind the scenes
- When an item’s created by and modified date are being initially set, they are being set to separate calls to time() (or whatever time library is being used) rather than one call, which depending on precision could lead to millisecond error differences.
@emmanuel Were there any undocumented changes to how times are tracked between January and now that could have caused this?