Skip to content
Tool

Wrangler

Official site

Playbooks for Wrangler

  1. Fixing D1 "no such table" after a migration that seemed to run

    Covers the two most common causes: applying a migration to the wrong local/remote target, and a Worker binding pointing at a different database_id than the one that was migrated. Does not cover a migration file that itself has a SQL error (that fails loudly at apply time, not later as "no such table"), or drift specifically caused by an ORM's own migration tracking — see the Drizzle-specific playbook for that. Also covers a preview_database_id on the binding sending wrangler dev to a different database from the one the migration was applied to.

    Unverifiedno reproductions yetWhy this confidence?
  2. Debugging Workers Error 1101 (uncaught exception)

    Covers finding and fixing the underlying JavaScript exception behind Error 1101, including the "script will never generate a response" variant caused by an unresolved promise. Does not cover Error 1102 (CPU time limit exceeded — a resource limit, not a thrown exception) or Error 1015 (rate limiting) — those have separate, more specific causes and remedies.

    Unverifiedno reproductions yetWhy this confidence?
  3. Fixing Workers CPU time limit exceeded (Error 1102)

    Covers genuine CPU-time exhaustion (heavy synchronous computation) and distinguishes it from a request that's merely slow because it's waiting on a subrequest — waiting time never counts toward CPU time, so that case needs a different fix entirely. Does not cover memory-limit resets (a different error, "Exceeded Memory") or the free-plan daily request cap (Error 1027).

    Unverifiedno reproductions yetWhy this confidence?
  4. Fixing wrangler d1 execute --remote hanging with no output

    Covers the interactive-confirmation-prompt cause (the most common one, especially in CI or piped/backgrounded shells) and network connectivity to the Cloudflare API as a secondary cause. Does not cover a command that's genuinely still running against a very large file — check for real progress (network/CPU activity) before assuming it's stuck.

    Unverifiedno reproductions yetWhy this confidence?

Versions