Workers SDK Issue Reports

← Back to Dashboard

#10452 "Would you like to report this error to Cloudflare?" too easy to accept by accident

Recommendation:KEEP OPEN
Difficulty:easy
Reasoning:

Confirmed bug in code: confirm() uses defaultValue=true for Enter key, but sentry code only sets fallbackValue=false (for CI). Cloudflare member also experiencing this, causing bogus error reports.

Suggested Action:

Fix sentry captureGlobalException to pass defaultValue: false to confirm()

View on GitHub →

Analysis Report

Issue Review: cloudflare/workers-sdk#10452

Summary

Error report prompt defaults to "yes" when Enter is pressed, causing accidental consent to share error reports.

Findings

  • Created: 2025-08-23
  • Updated: 2025-11-17
  • Version: wrangler 4.32.0 → 4.60.0 (current)
  • Component: wrangler (sentry/error reporting)
  • Labels: bug
  • Comments: 1 (from Cloudflare member confirming the issue)

Key Evidence

  1. Issue confirmed by Cloudflare member: @kentonv (MEMBER) commented that they also experience this and submit "a lot of bogus error reports" because of it.

  2. Bug verified in source code: The issue is a genuine code bug in packages/wrangler/src/sentry/index.ts. The captureGlobalException function calls:

    await confirm("Would you like to report this error...", { fallbackValue: false })

    However, fallbackValue only affects non-interactive/CI environments. The defaultValue parameter (which controls what happens when Enter is pressed in interactive mode) defaults to true in dialogs.ts.

  3. No fix found: No merged PRs reference this issue, and the changelog does not mention this issue number. The relevant code still has the bug as of the latest commit.

  4. Clear fix path: The fix would be to pass { defaultValue: false, fallbackValue: false } to the confirm call, or just { defaultValue: false }.

Recommendation

Status: KEEP OPEN

Reasoning: This is a confirmed, reproducible bug validated by both the reporter and a Cloudflare team member. The source code analysis confirms the bug exists - the confirm function uses defaultValue: true for interactive prompts, but the sentry code only sets fallbackValue: false (which only applies to non-interactive contexts). The fix is straightforward but has not been implemented.

Action: Prioritize fix - this bug causes noise in Sentry telemetry and violates user consent expectations.

Notes & Feedback (2)

anonymous - Jan 29, 2026, 02:49 PM
I left the comment: We intentionally default to [y] for submitting error reports to Sentry, to make it as easy as possible for users to send us them. One thing to note is that we do redact a lot of data from the report sent to Sentry. However, we're considering whether or not Sentry reports are useful at all in Wrangler. They have a very high false positive rate, and are mostly causing noise without actually helping us fix anything. I'm going to close this issue for now because we don't intend to change the default.

Add Note