worker2 doesn't see its D1 database when running multiple workers with one command.
worker2 doesn't see its D1 database when running multiple workers with one command.
Problem statement normalized from the linked evidence
CANDIDATE VIEW · NOT A PUBLISHED OPPORTUNITY
01
Qualification checklist
Gate decision: Aug 15, 2026
×
At least 3 independent users2 / 3
NOT MET
×
At least 2 independent discussions1 / 2
NOT MET
✓
At least 1 supporting signal1 Workarounds · Persistence
MET
02
Observed signals
Users2
Discussions1
Mentions2
Active days2
Source coverageGitHub
TrendUNKNOWN
First seenOct 29, 2025
Last seenAug 11, 2026
Why the gate is holding
Fewer than 3 independent users
Fewer than 2 independent discussions
Competition research, commercial scoring, and Build Gap analysis do not run until this gate passes.
03
Source evidence
2 evidence records
github · MEDIUM · Aug 11, 2026
cloudflare/workers-sdk
> [!NOTE] > This is an automated, advisory triage report generated by workers-devprod. It is not an official maintainer response — a maintainer will follow up. 🤖 Automated triage report # Issue Triage: cloudflare/workers-sdk#11121 ## Summary Running two workers with a single `wrangler dev -c worker1/... -c worker2/...` command, worker2 cannot see its D1 database, although it works when the worker is run on its own. ## Classification - **Type:** Bug - **Component:** `packages/wrangler` (multi-worker `wrangler dev`;…