Workers SDK Issue Reports

← Back to Dashboard

#10767 Cannot Create Pipelines Sink

Recommendation:KEEP OPEN
Difficulty:n/a
Reasoning:

Multiple bugs: unhelpful 500 error for token permissions, pipeline name validation mismatch. Tracked internally (PIPE-380).

Suggested Action:

Tracked internally; improve error messaging

View on GitHub →

Analysis Report

Issue Review: cloudflare/workers-sdk#10767

Summary

Creating pipeline sinks fails with "Internal Server Error 500" due to token permission/configuration issues.

Findings

  • Created: 2025-09-25
  • Updated: 2025-10-02
  • Version: wrangler 4.40.0 → 4.61.0
  • Component: pipelines
  • Labels: bug, internal, pipelines
  • Comments: 7

Key Evidence

  • User gets HTTP 500 error when creating R2 Data Catalog sink
  • Internal Jira ticket PIPE-380 raised by @petebacondarwin
  • Maintainer @oliy identified root cause: service token authentication error - token didn't have access to R2 bucket specified
  • Reporter claims token has correct permissions (R2 SQL:Read, R2 Data Catalog:Edit, R2 Storage:Edit)
  • Second user @lykhonis hit different issue: pipeline name validation regex mismatch (underscores required but OAuth flow rejects them)
  • Workaround found: create token directly via dashboard at https://dash.cloudflare.com/ACCOUNT_ID/r2/api-tokens using access id/secret directly

Recommendation

Status: KEEP OPEN

Reasoning: Multiple bugs uncovered: (1) unhelpful "Internal Server Error" instead of proper token permission error message, (2) pipeline name validation mismatch between CLI and OAuth flow. The internal label indicates this requires backend/platform support. Workarounds exist but UX is poor.

Action: Tracked internally (PIPE-380). Improve error messaging to surface actual permission issues rather than generic 500 error. Fix pipeline name validation consistency.

Suggested Comment

N/A - Already tracked internally with maintainer engagement.

Notes & Feedback (0)

No notes yet.

Add Note