GGT_UNSUPPORTED_SEARCH error with Gadget API on specific combination of search query and filter.
Hi Everyone,
I am having an issue where text search + date range filters fail on certain metafields but work on others. See the following scenarios where I tested to know what works and what doesn't:
❌ Fails:
Text search + filtering deliveryDate (metafield type date) with
All date fields use same filterkey (
lessThanOrEqual and greaterThanOrEqual keys.
Text search +filtering productionDate (metafield type date ) with lessThanOrEqual and greaterThanOrEqual keys.
✅ Works:
Text search + shopifyCreatedAt (native date field) with lessThanOrEqual and greaterThanOrEqual keys.
Text search + shippingZoneTitle (metafield type text)All date fields use same filterkey (
greaterThanOrEqual/lessThanOrEqual).
Has anyone seen this before and is there a specific limitation with search + range filters on metafields with type of date?
11 Replies
Hi @Chocci_Milk sorry for tagging you but just thought it would be best to get an answer from the Gadget team for an insight as to how to fix this.
Thanks!
Hello,
We're going to take a look at this really soon. Sorry for the wait
Ok, could you please share a traceId for the request and an example of the API call you're making so that I can take a look more closely/try to reproduce it. My suspicion is not that its a bug but just that what you're trying to do isn't possible
@Chocci_Milk here is a trace ID of my latest API request
0d47e8162056a4b8df04f7e4022de1fa
Hi Mike,
I am looking into this
Would you be able to share the used problematic queries in question?
From what I can put together here its likely the nested
and
I attempted to flatten the filter based on the screenshot provided and was able to get results.
filter: {
AND: [
{ cancelledAt: { isSet: false } },
{ cancelledAt: { isSet: false } },
{ productionDate: { greaterThanOrEqual: "2025-08-07T00:00:00.000Z" } }
]
}
});@[Gadget] Mark thank you for the response. I will try first your suggestion and will get back to you for updates.
Hi @[Gadget] Mark , I tried your suggestion of flattening the request and I am still getting the error unfortunately
Trace id is
bc85ee6aaa75042484d3c52432a26838
Hello @[Gadget] Mark , I'd like to follow up on this ^. Thank you!
We will take a look 👍
Hi Mike, unfortunately we have not been able to figure out a way to make this query work
@[Gadget] Mark , thank you for the effort of checking this.
With that being said, is this really a limitation?
It would be a big one since it is an important feature to be able to filter through a metafield (with date type) with other metafields.
Can you suggest some workarounds if ever?
Would you be able to share the exact query you're using?