RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Conductor] Fix Join task resolution when joinOn references a Switch/Decision task

Request to fix the Join task resolution logic when its `joinOn` list contains a reference to a Switch task, ensuring it waits on the correct terminal child task.

Original Source

@@nthmost-orkes | 0 pts | 2/26/2026

## Bug Description When a Join task's \`joinOn\` list contains a reference to a container task (like Switch), the Join waits on the container itself rather than its terminal child task. This causes Fork/Join workflows with nested Switch tasks to fail: ``` [Fork] / \ v v [SimpleTask] [Switch] --caseX--> [InnerTask] \ / v v [Join] ``` The Join waits on \`[branch1_simple, branch2_switch]\` but should resolve \`branch2_switch\` → \`branch2_simple_inside_switch\`. ## Proposed Solution Introduce a polymorphic \`getTerminalTaskRef()\` method in \`WorkflowSystemTask\`: - **Base implementation**: returns the task itself - **Switch override**: resolves to the terminal task within the selected case branch, supporting recursive nesting - **Join**: uses \`SystemTaskRegistry\` to polymorphically resolve container tasks in \`joinOn\` This follows the Open-Closed Principle — new containe

Discussion

Loading comments...