#9519 D1 crashes indefinitely when trying to export database with Virtual Tables (fts5)
Platform bug in D1 service (not wrangler). Export fails on FTS5 virtual tables and leaves database permanently inaccessible. Labeled `internal`. Multiple users affected.
No action - requires D1 backend team fix. Issue correctly tracked with `internal` label.
Analysis Report
Issue Review: cloudflare/workers-sdk#9519
Summary
D1 export with virtual tables (FTS5) fails and leaves the database permanently inaccessible.
Findings
- Created: 2025-06-07
- Updated: 2025-06-30
- Version: 4.19.1 → 4.60.0 (wrangler, but irrelevant - this is a platform bug)
- Component: D1 (platform service)
- Labels: bug, internal, d1
- Comments: 2 (users confirming the issue)
Key Evidence
- Platform bug, not wrangler bug: The
internallabel indicates this requires Cloudflare Platform support. The error messages ("cannot export databases with Virtual Tables (fts5)" and "Currently processing a long-running export") originate from the D1 service, not wrangler. - No fix found: No merged PRs reference this issue. Not mentioned in wrangler changelog.
- Critical impact: Database becomes completely inaccessible after a failed export attempt - won't respond to queries and won't load in dashboard.
- Multiple users affected: 2 commenters confirm the issue. One user contacted support and Discord.
- Cannot reproduce locally: This is a D1 platform service issue - wrangler just proxies commands to the D1 API. No local reproduction is possible.
Recommendation
Status: KEEP OPEN
Reasoning: This is a valid, unresolved bug in the D1 platform service (not wrangler). The internal label correctly indicates it needs Cloudflare Platform team involvement. The issue causes critical data availability problems where a database becomes permanently inaccessible after a failed export. Multiple users are affected.
Action: Keep open. This issue is correctly tagged with internal and is waiting for Cloudflare's D1 platform team to address the export lock state handling. No wrangler changes can fix this - it requires backend D1 service changes.
Notes & Feedback (0)
No notes yet.