Add docs for multi-team triggerer support#67608
Open
ramitkataria wants to merge 1 commit into
Open
Conversation
Add a `Team-scoped Triggerer` section to the multi-team documentation covering the `--team-name` CLI argument, behavior for team-scoped vs global triggerers, interaction with `--queues`, and an example deployment. Add a tip in the deferring docs pointing users toward `--team-name` as the native multi-team solution alongside the existing `--queues` docs. Remove `Async support` from the `Work in Progress` list since team-scoped triggerer support is now implemented/in PR.
vincbeck
approved these changes
May 27, 2026
o-nikolas
reviewed
May 27, 2026
| Team-scoped Triggerer | ||
| --------------------- | ||
|
|
||
| When Multi-Team mode is enabled, the triggerer can be scoped to a specific team using the ``--team-name`` CLI argument. A team-scoped triggerer only processes deferred tasks (triggers) belonging to that team's Dags. This allows teams to run isolated triggerer instances with independent capacity and failure domains. |
Contributor
There was a problem hiding this comment.
Should be? Otherwise team triggers aren't going to run, right?
Suggested change
| When Multi-Team mode is enabled, the triggerer can be scoped to a specific team using the ``--team-name`` CLI argument. A team-scoped triggerer only processes deferred tasks (triggers) belonging to that team's Dags. This allows teams to run isolated triggerer instances with independent capacity and failure domains. | |
| When Multi-Team mode is enabled, a triggerer should be scoped to each specific team using the ``--team-name`` CLI argument. A team-scoped triggerer processes deferred tasks (triggers) belonging to that team's Dags. This allows teams to run isolated triggerer instances with independent capacity and failure domains. |
|
|
||
| .. note:: | ||
|
|
||
| If you use both ``--team-name`` and ``--queues``, ensure that each combination of team and queue has at least one triggerer running, or triggers matching that combination will remain unassigned until one starts. |
Contributor
There was a problem hiding this comment.
This is true for each individually as well right?
Comment on lines
+548
to
+561
| Example Deployment | ||
| ^^^^^^^^^^^^^^^^^^ | ||
|
|
||
| A deployment with two teams and a shared set of Dags with no team: | ||
|
|
||
| .. code-block:: bash | ||
|
|
||
| # Team-scoped triggerers | ||
| airflow triggerer --team-name team_a | ||
| airflow triggerer --team-name team_b | ||
|
|
||
| # Global triggerer for Dags without a team | ||
| airflow triggerer | ||
|
|
Contributor
There was a problem hiding this comment.
This feels superfluous to me, I'd just drop it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a
Team-scoped Triggerersection to the multi-team documentation covering the--team-nameCLI argument, behavior for team-scoped vs global triggerers, interaction with--queues, and an example deployment.Add a tip in the deferring docs pointing users toward
--team-nameas the native multi-team solution alongside the existing--queuesdocs.Remove
Async supportfrom theWork in Progresslist since team-scoped triggerer support is now implemented/in PR.Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.