Saw in the release it was advertised as increased limits but am I correct in seeing that the app definitions limit has been reduced to 128?
A bit surprised there was no notice for this, this close to BFCM and we have large merchants using way more than 128 already and trying to think through how we get them out of the hole here.
Anyone else seeing the same?
1 Like
Is it possible to request an exception here for certain Plus Merchants? Want to avoid their live experiences breaking and having to refactor all our metafields this close to BFCM.
We are investigating, Daniel. Will get back to you ASAP.
Thanks James,
As far as we can tell we had a limit of 250. It was reduced to 128 last thursday.
We have several large merchants that had 170+ and now we can’t create any further definitions for them - which has material impact.
We are taking steps to mitigate where we can, but no real notice for us and everyone is going into BFCM so ramping up.
Larger merchants doing more complex stuff need more definitions.
We have increased the Metaobject definitions per app to 256 (from 128). This should alleviate your near-term concerns.
Previously all apps shared the same Merchant pool of available Metaobject definitions (and a Metafield definition limit by resource type) and the definition caps were slightly higher overall. So it was still a large overall increase in potential definitions for a Merchant and was a slightly reduced definition count for apps.
1 Like
Thank you James, really appreciate it!
Will do our part to reduce the bloat in the definitions but really appreciate the lift and help here.
No worries. It was clearly the right thing to do. Thanks for bringing it to our attention.