# X_RUNTIME_DRIVER_SPLIT

## Means

the ambient driver is not the one this process serves

## Typical cause

an app module installing a driver itself at import time (before 31.0.0, `setJobDriver()`). `startServices` builds the drivers and **captures** them, and `loadApp` runs after it — so the ambient slot moves and the captured object does not: the worker claims from what was captured while every `handle.enqueue()` publishes to what is ambient. Jobs are accepted, acknowledged, visible in `/_x` and never run. Refused at boot, because the alternative is a deployment that only ever looks healthy

## Fix

`export const runtime = { <driver>: yourDriver } satisfies RuntimeOverrides;` in `apps/web/runtime.ts` — and delete the module's own install call

[CLI and verify](/error-codes#cli-and-verify)