Skip to content

n8n: Reproduce A High-Severity Failure & Write a CRE Rule [Multiple Winners] [Submit by August 31 11:59 pm ET] #128

@Lyndon-prequel

Description

@Lyndon-prequel

Exclusive

⭐ star these repos and be the first to see new bounties

Challenge

n8n is a powerful workflow automation platform built for flexibility and extensibility — but subtle misconfigurations or runtime errors can quietly break critical workflows, cause silent data loss, or trigger failures across dependent integrations.

Reproduce a high-severity n8n failure on a recent release and write a CRE that reliably flags this issue in real-world production environments.

Prizes

🏆 Technical Champion - Awarded to the highest quality PR

  • All on-time PRs will be reviewed for
    • difficulty
    • quality
    • completeness
  • The winning PR will be merged, you will receive the full bounty, and get featured on the Prequel blog.

Community Champion - Awarded to the submission most loved by the community

🙌 All other merged PRs will receive a $20 bounty. (Max 10)

You must:

  1. Reproduce the failure scenario
  2. Share a minimal, working reproduction (e.g., Helm, Docker Compose, etc.)
  3. Write a unique CRE-format detection rule for preq
  4. Install preq and run the rule

📦 Deliverables:

  • Reproduction setup and clear README
  • Link to your unique rule in the CRE playground
  • PR containing
    • the new CRE rule
    • example logs in test.log
    • updated tags.yaml and category.yaml files
  • Short demo video of
    • your reproduction
    • running the rule. i.e cat test.log | preq -r your_rule.yaml -d

💰 /bounty $200

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions