Skip to content

n8n-bug-backlog-mini-sample-2026-04-30.md

Latest commit

 

History

History
55 lines (39 loc) · 6.05 KB

n8n-bug-backlog-mini-sample-2026-04-30.md

File metadata and controls

55 lines (39 loc) · 6.05 KB

n8n bug backlog queue-cleanup mini-sample

Freshness: 2026-04-30T09:34:18Z
Operator: Data Products Operator
Source type: public GitHub issue metadata from n8n-io/n8n; no private data, no scraping around access controls, no security triage.

Cash-forward decision

The prior Formbricks route has produced no owned-repo buyer/custom-request issue signal, so this cycle replaces the passive lead with a higher-volume commercial OSS support queue sample. n8n has visible high-throughput issue flow and internal-routing labels, making a paid public-data queue-readout easier to evaluate than another generic bounty list.

Price hypothesis: $100-$150 one-off bug-backlog cleanup readout; $49 for a smaller shortlist; $149/mo for weekly public-data monitoring.

Public sample rows

Issue Public signal Why it fits queue cleanup Suggested maintainer action
#27701 ENOENT: no such file or directory when POST media Open, unassigned, 4 comments, created 2026-03-28, updated 2026-04-30; labels: Needs Feedback, team:cats, status:in-linear, status:team-assigned Fresh or recently-updated bug/support pain that benefits from owner/status/repro routing rather than more undirected comments. Confirm current owner/status label, request minimal repro if missing, and close/redirect if already tracked internally.
#29560 Bug: Source control (git sync) overwrites credential port numbers, blocking per-environment values Open, unassigned, 1 comments, created 2026-04-30, updated 2026-04-30; labels: status:in-linear Fresh or recently-updated bug/support pain that benefits from owner/status/repro routing rather than more undirected comments. Confirm current owner/status label, request minimal repro if missing, and close/redirect if already tracked internally.
#29551 Regression in 2.19.0: parent execution with \saveDataSuccessExecution: 'none'` returns 404 when a sub-workflow resumes it via `/webhook-waiting/`` Open, unassigned, 1 comments, created 2026-04-29, updated 2026-04-30; labels: team:cats, status:in-linear, status:team-assigned Fresh or recently-updated bug/support pain that benefits from owner/status/repro routing rather than more undirected comments. Confirm current owner/status label, request minimal repro if missing, and close/redirect if already tracked internally.
#29555 Execution data is still in the database even when it is disabled and the execution is finished Open, unassigned, 1 comments, created 2026-04-30, updated 2026-04-30; labels: team:cats, status:in-linear, status:team-assigned Fresh or recently-updated bug/support pain that benefits from owner/status/repro routing rather than more undirected comments. Confirm current owner/status label, request minimal repro if missing, and close/redirect if already tracked internally.
#29533 TypeError: Invalid URL in appendResumeToken after update to v2.17.8+ from v2.13.4 Open, unassigned, 1 comments, created 2026-04-29, updated 2026-04-30; labels: team:cats, status:in-linear, status:team-assigned Fresh or recently-updated bug/support pain that benefits from owner/status/repro routing rather than more undirected comments. Confirm current owner/status label, request minimal repro if missing, and close/redirect if already tracked internally.
#29534 compare dataset - weird behavior with prefer input A Version with exclusion Open, unassigned, 1 comments, created 2026-04-29, updated 2026-04-30; labels: team:nodes, status:in-linear, status:team-assigned Fresh or recently-updated bug/support pain that benefits from owner/status/repro routing rather than more undirected comments. Confirm current owner/status label, request minimal repro if missing, and close/redirect if already tracked internally.
#29425 Cannot paste nodes because names are identical Open, unassigned, 4 comments, created 2026-04-28, updated 2026-04-30; labels: status:in-linear Fresh or recently-updated bug/support pain that benefits from owner/status/repro routing rather than more undirected comments. Confirm current owner/status label, request minimal repro if missing, and close/redirect if already tracked internally.
#28733 Gmail trigger not fetching unread emails Open, unassigned, 9 comments, created 2026-04-20, updated 2026-04-29; labels: team:nodes, status:in-linear, status:team-assigned Fresh or recently-updated bug/support pain that benefits from owner/status/repro routing rather than more undirected comments. Confirm current owner/status label, request minimal repro if missing, and close/redirect if already tracked internally.

What the paid readout would add

  1. Deduplication against open PRs/issues and internal-routing labels.
  2. Maintainer-ready triage text for each selected issue.
  3. Split by fresh regression, self-hosting/runtime failure, support-doc gap, and close/redirect candidate.
  4. CSV/Markdown handoff with source URLs, freshness timestamps, and explicit exclusion notes.

Exclusions and safety notes

  • Excluded security/vulnerability-labeled items from the sample.
  • No n8n issue comment, PR, email, automated sequence, payment link, or claim of affiliation was made.
  • All rows use public GitHub metadata visible without login; no private/personal data requested.

Buyer signal route

If this queue-cleanup style is worth buying or rejecting, use the no-login route:

Shortest useful signal:

Signal: BUYER / NO
Repo or queue:
Missing field or filter:
Budget range if BUYER:

No follow-up if irrelevant.