Operation didn't take effect

If you saved an operation but the checkout still shows the old behaviour, work through this list before reaching out to support.

1. Is the change still publishing?

After you save, a background job publishes the change to the function’s metafield. The home dashboard and the operation list show the job’s status while it runs. If the status is:

Pending or Running — wait a few seconds. Most jobs finish within 5 seconds. The very first publish after install can take up to 30 seconds.
Failed — the toast stays visible with the error message. The app retries automatically; if it keeps failing, contact support.

See Publishing changes for the full lifecycle.

2. Is the operation enabled?

Open the operation’s edit form. If the enable toggle is off, the operation is in the database but doesn’t run. Turn it on and save.

3. Are the conditions matching?

Conditions are evaluated against the actual cart at the time the function runs. Walk through each one:

Field type matches. A country_code condition expects an ISO 3166-1 alpha-2 code (US, not United States).
Operator is right. equals is exact-match. contains is loose. For ranges, use between and check the bounds.
The value is what you think it is. Use a quick test: temporarily turn off all conditions. If the operation fires without conditions, the issue is the condition, not the action. Re-enable them one at a time.

For more, see Conditions and Condition fields.

4. Does the rate or method name match?

The match is exact and is checked against the customer-facing name at checkout. If the rate is named Standard Shipping in Shopify admin, the match field expects Standard Shipping — not standard, not Standard shipping, not Standard-Shipping. Whitespace and case matter.

If you’ve already renamed the rate with another operation, the next operation sees the post-rename name. See Order of operations.

5. Is the right plan feature available?

Some operations require a feature the plan doesn’t include. For example:

Lowest and Highest modes for shipping hide require Advanced or Pro. The form shows an “Upgrade to Advanced plan” hint next to the option.
Multi-locale rename translations beyond the primary locale require a plan that includes localization.

The form prevents saving an operation that uses a gated feature, but if you downgraded your plan after creating the operation, the operation continues to run on the feature it was created with — until you edit it.

6. Is the operation limit blocking creation (not running)?

The operations limit prevents creating new operations, not running existing ones. If the limit is reached, the Create Operation button is disabled and a banner shows. Existing operations continue to run.

7. Is the function registered on the store?

If you can’t see the change at all (no error, but the old behaviour persists), the function may not be registered with Shopify. This usually fixes itself after the first publish, but if it doesn’t:

Open the home dashboard. The “Set up” indicator shows if the function isn’t registered.
Re-save any operation. The publish job also re-registers the function.

If the indicator stays on after re-saving, contact support.

8. Caching at checkout

Shopify caches checkout options for the duration of a cart session. If you saved a change and then went straight to checkout with a cart you already had open, the cart may still be using the old configuration. Refresh the cart (or start a new one) to pick up the new configuration.

Still stuck?

Contact support. Include the operation name, what you expected to happen, and what actually happened.