Hi @Shirobachi, just wanted to drop a quick note to confirm I could reproduce this, even with a brand new setup. I have documented this in our internal bug tracker and we will, of course, confirm once this has been resolved.
I was able to avoid running into this error when defining a JSON filter though instead of using the manual filters like so:
My exact value used for Filters (JSON) was this one (where Date is the name of my date field):
{
"or": [
{
"property": "Date",
"date": {
"on_or_after": "2021-12-31T23:00:00.000Z"
}
}
]
}