Hey @talktohenryj,
Thanks for the detailed report and for including the extensions.search output.
Can you test wrapping your timestamp in single quotes? We’ve had similar reports before where this has solved it:
created_at:>='2025-12-03T13:01:34-05:00'
Without quotes, the colons in your timestamp are being interpreted as field:value delimiters.The quotes should prevent the parser from splitting on the colons within your timestamp value.
The search syntax docs do note that “date values must be a string surrounded by quotes” but the examples (as you’ve shown) aren’t always consistent. Let me know if that works for you and then I’ll flag this for a documentation update.