Dynamic complexity cost for `metafieldsSet` mutation

The changelog entry describes a change to how the metafieldsSet mutation is priced, moving from a flat cost to dynamic complexity costing based on the number of distinct resources changed. It notes most apps won’t need changes, but apps writing across many owners may hit rate limits and are encouraged to batch writes by distinct resource.

Dynamic complexity cost for `metafieldsSet` mutation The metafieldsSet mutation now uses dynamic complexity costing. Instead of a flat cost for every call, a request's cost reflects how many distinct resources metafields were changed. Most apps need no changes, as updating a single resource remains cheap. Apps setting many metafields across many different owners may hit their rate limit faster. Apps are encouraged to batch metafield writes by distinct resource. What changed Previously, every metafieldsSet call cost a flat 10 points, regardless of…

Vendor source ↗

The evidence describes a changelog entry for Shopify: metafieldsSet mutation now uses dynamic complexity costing instead of a flat cost, affecting pricing/limits as cost scales with number of distinct resources changed. It notes that most apps require no changes, but batch writes are encouraged; current text mentions a change from a flat 10 API points to a dynamic cost. There is no explicit deadline or replacement endpoint provided in the evidence.

Dynamic complexity cost for `metafieldsSet` mutation The metafieldsSet mutation now uses dynamic complexity costing. Instead of a flat cost for every call, a request's cost reflects how many distinct resources metafields were changed. Most apps need no changes, as updating a single resource remains cheap. Apps setting many metafields across many different owners may hit their rate limit faster. Apps are encouraged to batch metafield writes by distinct resource. What changed Previously, every metafieldsSet call cost a flat 10 api points, regardless…

Vendor source ↗