Cloudflare / Cloudflare

Cloudflare D1 migrations_dir Does Not Support Recursive SQL File Search

Fix Cloudflare D1 wrangler not finding migration SQL files in subdirectories Includes evidence for Cloudflare troubleshooting demand.

Source-backed Last updated May 13, 2026 1 source Needs local verification

Category: Cloudflare
Error signature: D1 migrations_dir recursive SQL file search not supported
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 13, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Cloudflare, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

D1 migrations_dir recursive SQL file search not supported is a Cloudflare failure pattern reported for developers trying to fix cloudflare d1 wrangler not finding migration sql files in subdirectories. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

wrangler D1 migrations only reads flat directories, not recursive. Drizzle ORM v1 uses per-migration subdirectories. Blocks Cloudflare D1 adoption for projects using modern ORMs.

Common causes

Drizzle ORM v1+ stores migrations in individual subdirectories, but wrangler only reads flat migration directories — breaks modern ORM migration workflows
wrangler D1 migrations only reads flat directories, not recursive. Drizzle ORM v1 uses per-migration subdirectories. Blocks Cloudflare D1 adoption for projects using modern ORMs.

Quick fixes

Confirm the exact error signature matches D1 migrations_dir recursive SQL file search not supported.
Check the Cloudflare account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match D1 migrations_dir recursive SQL file search not supported exactly before applying the quick fix.
Compare the failing environment with Cloudflare versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does D1 migrations_dir recursive SQL file search not supported mean in Cloudflare?

D1 migrations_dir recursive SQL file search not supported indicates the workflow described by "Cloudflare D1 migrations_dir Does Not Support Recursive SQL File Search" failed in a Cloudflare context. Start by confirming the exact signature and the component that emitted it.

What should I check first for D1 migrations_dir recursive SQL file search not supported?

Check whether this cause matches your environment: Drizzle ORM v1+ stores migrations in individual subdirectories, but wrangler only reads flat migration directories — breaks modern ORM migration workflows

Is the D1 migrations_dir recursive SQL file search not supported guidance source-backed?

The "Cloudflare D1 migrations_dir Does Not Support Recursive SQL File Search" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for D1 migrations_dir recursive SQL file search not supported?

For "Cloudflare D1 migrations_dir Does Not Support Recursive SQL File Search", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging D1 migrations_dir recursive SQL file search not supported?

For "Cloudflare D1 migrations_dir Does Not Support Recursive SQL File Search", collect the failing Cloudflare command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.