Repository navigation
run-many --parallel option not honored when one (or more) targets depend on continuous task #31494
Description
Activity
- added a commit that references this issue
on Jun 8, 2025 - addedscope: corecore nx functionalitycore nx functionalitypriority: mediumMedium Priority (not high, not low priority)Medium Priority (not high, not low priority)
on Jun 19, 2025 Hey, we are facing the same issue. We have to run our e2e test with
--parallel=1, but after migrating to Nx 21 and continuous tasks, the parallel option is not honored anymore. We've tried usingaffectedinstead, but same result. However, dropping thecontinuousproperty seems to fix the issue. This issue will prevent us from running a lot of (continuous) tasks in the DTE.github-actions commented
on Mar 12, 2026 on Mar 12, 2026 – with GitHub ActionsContributorMore actionsThis issue has been automatically marked as stale because it hasn't had any activity for 6 months.
Many things may have changed within this time. The issue may have already been fixed or it may not be relevant anymore.
If at this point, this is still an issue, please respond with updated information.
It will be closed in 21 days if no further activity occurs.
Thanks for being a part of the Nx community! 🙏- added a commit that references this issue
on Mar 21, 2026 - added a commit that references this issue
on Mar 26, 2026 - added a commit that references this issue
on Apr 6, 2026 github-actions commented
on Apr 21, 2026 on Apr 21, 2026 – with GitHub ActionsContributorMore actionsThis issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
- locked as resolved and limited conversation to collaborators
on Apr 21, 2026
Current Behavior
When executing
npx nx run-many -t target1 target2 --parallel=1, the targets are not serialized and instead run concurrently if one (or more) of the targets depends on acontinuoustarget.Expected Behavior
Only one target should execute at a time given
--parallel=1regardless of whether of whether or notcontinuousis involved in the target dependency chain.GitHub Repo
https://github.com/techfg/nx-21-continuous-tasks-repros
Steps to Reproduce
git clone https://github.com/techfg/nx-21-continuous-tasks-repros.gitnpx nx run-many -t first second third --parallel=1Actual Behavior:
firstandsecondexecute and thenthirdexecutes afterfirst and secondare completenpx nx run-many -t third fourth --parallel=1Actual Behavior:
thirdandfourthexecute concurrentlyNx Report
Failure Logs
Package Manager Version
npm 10.9.2
Operating System
Additional Information
--parallel=1is properly honored when none of the targets depend on acontinuoustask. For example, executingnpx nx run-many -t first secondwill serialize the execution of the targets as expected