gatsbyjs/gatsby · error

${message} Continuing build using without using any adapter

Error message

${message}

Continuing build using without using any adapter due to GATSBY_CONTINUE_BUILD_ON_MISSING_ADAPTER environment variable being set

What it means

In handleAdapterProblem, when zero-configuration adapter deployment fails (adapter missing or mismatched), the build normally panics. If GATSBY_CONTINUE_BUILD_ON_MISSING_ADAPTER is set, this warning replaces the panic: the build continues without any adapter, so adapter-specific optimizations (caching headers, DSG/SSR routing) will be absent from the deployment.

Source

Thrown at packages/gatsby/src/utils/adapter/init.ts:122

      }
    }
  } catch (e) {
    return {
      found: false,
    }
  }
}

const handleAdapterProblem = (
  message: string,
  panicFn = reporter.panic
): never | undefined => {
  if (!process.env.GATSBY_CONTINUE_BUILD_ON_ADAPTER_MISMATCH) {
    panicFn(
      `${message}\n\nZero-configuration deployment failed to avoid potentially broken deployment.\nIf you want build to continue despite above problems:\n - configure adapter manually in gatsby-config which will skip zero-configuration deployment attempt\n - or set GATSBY_CONTINUE_BUILD_ON_MISSING_ADAPTER=true environment variable to continue build without an adapter.`
    )
  } else {
    reporter.warn(
      `${message}\n\nContinuing build using without using any adapter due to GATSBY_CONTINUE_BUILD_ON_MISSING_ADAPTER environment variable being set`
    )
  }
  return undefined
}

export async function getAdapterInit(
  currentGatsbyVersion: string = gatsbyVersionFromPackageJson
): Promise<AdapterInit | undefined> {
  // 0. Try to fetch the latest adapters manifest - if it fails, we continue with manifest packaged with current version of gatsby
  const latestAdapters = await getLatestAdapters()

  // 1. Find adapter candidates that are compatible with the current environment
  //    we find all matching adapters in case package is renamed in the future and future gatsby versions will need different package than previous ones
  const adapterEntry = latestAdapters.find(candidate => candidate.test())

  if (!adapterEntry) {
    reporter.verbose(

View on GitHub (pinned to e85d62f177)

Solutions

1. Install and configure the platform adapter manually in gatsby-config.js so zero-configuration deployment is skipped
2. Verify the adapter module name and version match the deployment platform
3. Remove GATSBY_CONTINUE_BUILD_ON_MISSING_ADAPTER once the adapter is configured so real problems panic again

When it happens

Trigger: Thrown at packages/gatsby/src/utils/adapter/init.ts:122 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of gatsbyjs/gatsby@e85d62f177 (2026-08-26). Data as JSON: /api/errors/4d1cb81f4d5d1b1e. Report an issue: GitHub.