Exclusive > timestamp filters exclude the full second
Shopify developer change
MerchantDiff detected this entry in Shopify's official developer changelog on October 19, 2026.
This Shopify update is categorized as API, Update, GraphQL Admin API, 2026-10.
What changed
The GraphQL Admin API returns timestamps such as createdAt to the second, but internally some resources store them with fractional seconds. Before 2026-10, created_at:>'2026-09-15T12:00:02Z' compared against 12:00:02.000000. It returned records from later in that second, and the response showed those records with createdAt: "2026-09-15T12:00:02Z". The same records also matched created_at:<='2026-09-15T12:00:02Z'. As of 2026-10, when a > value has no fractional seconds, the filter starts after the end of that second (12:00:02.999999).
Who is affected
Apps that send a > bound without fractional seconds on a timestamp filter in the query argument of a GraphQL Admin API connection, for example created_at on the orders query.
What action may be needed
Apps on 2026-07 or earlier don't need to change anything. Before you move an app to 2026-10, check its > filters: Find queries that pass a timestamp from an earlier response as a > bound, for example to fetch records newer than the last record that the app saw. If the app must not miss records created later in that same second, use >= with that timestamp and remove duplicates by id.
Use the official Shopify entry below as the source of truth for technical implementation details, affected APIs, migration instructions and deadlines.
Want the actionable version?
MerchantDiff monitors Shopify API changes, deprecations, deadlines and ecosystem updates, then turns them into developer-focused release intelligence: what changed, who is affected and what action may be needed.
Get MerchantDiff →