Skip to content

Shopify Dude Fix

Shopify Bulk Operation Access Denied After 31 Days? Re-enable the Right Permission

Partner-built Shopify apps now need separate bulk query and mutation permissions. Diagnose access denied errors, 31-day lapses, and safe reruns.

Quick answer: Since November 6, 2026, partner-built Shopify apps must have explicit access to the type of GraphQL bulk operation they start. Check Partner Dashboard → Apps → your app → API access requests → Run bulk operations. Enable Allow bulk queries for bulkOperationRunQuery and Allow bulk mutations for bulkOperationRunMutation. A job that has been idle for 31 days may need its permission re-enabled.
On this page

Why a previously working export suddenly fails

This is a platform-level authorization check, not an API-version change. It applies to all GraphQL Admin API versions. Shopify pre-enabled recently used bulk-operation types, but removes access to a type after 31 days without starting that type. A nightly product export can keep working while a quarterly bulk price update fails: read and write permissions are separate.

The rule covers public apps and custom apps built by partners. Merchant-created apps in Shopify admin or the Dev Dashboard are not affected at this time. This is distinct from the new IP allowlist requirement; passing an IP check does not grant bulk-operation access.

Fix the permission before changing code

  1. Identify whether the failing call is bulkOperationRunQuery or bulkOperationRunMutation.
  2. Open the app in the Partner Dashboard, then API access requests.
  3. Under Run bulk operations, enable only the required operation type or both if the integration genuinely uses both.
  4. Confirm that the app still has ordinary Admin API scopes for the resources it reads or changes.
  5. Retry a small, non-destructive operation and inspect both top-level GraphQL errors and userErrors.

No app version release, configuration change, or merchant reinstall is needed for this permission. It applies across the app’s installed stores.

Minimal bulk query smoke test

mutation {
  bulkOperationRunQuery(query: """
    { products { edges { node { id title } } } }
  """) {
    bulkOperation { id status }
    userErrors { field message }
  }
}

Run this only on a development shop where the app has product-read permission. A returned operation ID proves the start request was accepted; it does not prove that the asynchronous export completed. Check the operation status and output separately. A field-level ACCESS_DENIED during execution may still indicate missing resource scopes rather than the new app-level permission.

Make infrequent jobs operationally safe

Document which jobs use bulk reads and writes, especially quarterly ERP imports, seasonal catalog migrations, and one-off reindexing. Check access before planned runs, alert on access-denied start failures, and do not automatically repeat a partially completed bulk mutation until you have reconciled which records were changed. Do not assume that a successful bulk query authorizes a bulk mutation.

Common misunderstanding: Downgrading the Admin API or reinstalling the app will not bypass the new permission gate. Nor does a successful regular GraphQL query prove bulk-operation access is enabled.

How to test this

  1. On a partner-built development app, inspect the query and mutation access flags independently.
  2. Start a minimal bulk query and confirm an operation ID is returned without authorization errors.
  3. Poll the returned operation until it reaches a terminal status; inspect its output or error code.
  4. Test a separate bulk mutation only in a safe sandbox with reversible test data.
  5. Check that the job surfaces access denied clearly and does not mark a failed or partial run as complete.
  6. For jobs that run less than monthly, add a preflight permission review to the runbook.