If you see Sync failed, match the error message to a fix below. BlockCart may show technical English words in these messages, even if you use the app in another language. Messages from Shopify and numbers in the examples can vary.
For where to find the message and how to retry after a fix, see Understand sync status and retry a failed sync.
Checkout rule errors
| Error message | What it means | What to do |
| ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Condition cart-attribute with operator equal-to is not available for this input type. | A condition does not work with this rule's Rule input. The condition and operator in your message may differ. | Remove that condition or create a rule with a compatible Rule input. See A condition isn't available for my rule type. |
| Condition cart-attribute with operator equal-to is not supported by the checkout validation Function yet. | The saved condition or operator cannot run for this rule. The names in your message may differ. | Change or remove the named condition, save, and retry. |
| Condition cart-attribute requires an attribute key. | A cart or line item attribute condition has no key. Your message may say cart-items-attribute. | Enter the attribute key in the condition, then save. |
| Condition cart-attribute supports one attribute key per rule. | The rule uses more than one key for the same attribute condition. Your message may say cart-items-attribute. | Use one key for that attribute condition in this rule, or split the conditions into separate rules. |
| Shopify did not return a validation id. | Shopify did not confirm creation of the checkout rule. | Retry. If it repeats, contact support. |
| Shopify Admin API returned no data. or Unknown Shopify validation sync error. | BlockCart did not get a usable response or error detail. | Retry. If it repeats, contact support. |
| A Shopify message, sometimes starting with a field name such as validation.title:, or several messages separated by ; | Shopify rejected the create, update, or removal request. | Correct the field named in the message if you can. Otherwise retry, then contact support with the full message. |
Payment rule errors
| Error message | What it means | What to do |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Blocking cross-profile conflict: | Active rules under different Rule inputs may change the same payment method. The rest of the message names the inputs and actions. | Follow Fix payment rule conflicts between profiles, then sync each affected input. |
| Configuration rejected before Shopify: The compiled cart configuration is 10001 bytes, which exceeds the 10000-byte Function configuration limit. Reduce the number of active rules. | The combined active Cart rules are too large. The input and byte count can differ. | Reduce active rules or simplify their conditions and actions for that Rule input, then sync. |
| Configuration rejected before Shopify: The customerTags input variable needs 101 elements, which exceeds Shopify's limit of 100. | A combined list of tags, products, or collections is too long. The list name and count can differ. | Remove values from active rules using that Rule input until the combined list has at most 100 distinct values, then sync. |
| Configuration rejected before Shopify: Active cart rules reference 2 different cartAttribute keys, but one input profile can query only one per checkout run. Consolidate the rules or use a single key. | Active rules using one Rule input reference different attribute keys. The input, count, and key type can differ. | Use the same attribute key across those rules, or turn off or consolidate the affected rules. |
| Configuration rejected before Shopify: One or more active rules contain incomplete or unsupported actions. | An active payment rule has an action BlockCart cannot use. | Open the rules using that Rule input, complete or replace any unfinished action, save, and sync. |
| Shopify rejected the payment customization mutation: | Shopify rejected the payment change. The rest of the message is Shopify's reason. | Follow any specific instruction in Shopify's message. If there is none, retry and contact support if it repeats. |
| Shopify Admin GraphQL request failed: | Shopify did not return a usable response. The rest of the message gives its error, or says Unknown Admin GraphQL failure. | Retry. If it repeats, contact support with the full message. |
| Shopify rejected the payment customization deletion: | Shopify rejected removal of a payment customization, which can happen when billing access ends. The rest is Shopify's reason. | Check your subscription, then contact support if the removal keeps failing. |
| paymentCustomizationCreate returned no payment customization or paymentCustomizationUpdate returned no payment customization | Shopify did not confirm the new or updated payment change. These appear after Shopify rejected the payment customization mutation:. | Retry. If it repeats, contact support. |
| This shop already has 25 active BlockCart payment customizations, which is Shopify's per-store maximum. Deactivate one before syncing again. | The shop has reached the active payment customization limit. | Set every rule under an unneeded Rule input to Off, then sync again. |
If BlockCart says Subscribe to a premium plan before changing payment rules. or Subscribe to a premium plan before saving checkout rules., choose a plan before saving or syncing. See Plans and pricing: monthly vs yearly. These billing messages can stop an attempt before it becomes a failed sync.
Related articles
- Understand sync status and retry a failed sync
- Fix payment rule conflicts between profiles
- Plans and pricing: monthly vs yearly
Still failing? Contact support
Use Contact support. Include the rule name, the full error message, and a screenshot.