Skip to content

docs(workflows): fix stale FanOutStep docstring claiming sequential-only execution #3639

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mnriem merged 1 commit into from
Jul 22, 2026
+4 −3
Merged

docs(workflows): fix stale FanOutStep docstring claiming sequential-only execution #3639

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions src/specify_cli/workflows/steps/fan_out/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,10 @@ class FanOutStep(StepBase):
"""Dispatch a step template for each item in a collection.

The engine executes the nested ``step:`` template once per item,
setting ``context.item`` for each iteration. Execution is
currently sequential; ``max_concurrency`` is accepted but not
enforced.
setting ``context.item`` for each iteration. ``max_concurrency``
controls parallelism: ``<= 1`` (the default) runs items
sequentially, while ``> 1`` runs up to that many items concurrently
on a bounded thread pool (see ``WorkflowEngine._run_fan_out``).
"""

type_key = "fan-out"
Expand Down