Repository navigation
Conversation
ashb
added this pull request to stack #74339
October 6, 2026 15:06
kaxil
reviewed
Oct 6, 2026
ashb
force-pushed
the
task-loops-stack-7
branch
from
October 7, 2026 13:57
43debd4 to
3f2fff3
Compare
ashb
removed this pull request from stack #74339
October 7, 2026 15:20
ashb
force-pushed
the
task-loops-stack-7
branch
from
October 7, 2026 15:22
3f2fff3 to
2cd460c
Compare
ashb
added this pull request to stack #74410
October 7, 2026 15:22
ashb
force-pushed
the
task-loops-stack-7
branch
2 times, most recently
from
October 7, 2026 20:57
15a1960 to
a6d33c8
Compare
ashb
force-pushed
the
task-loops-stack-7
branch
from
October 8, 2026 13:56
a6d33c8 to
cc4f2a3
Compare
ashb
force-pushed
the
task-loops-stack-7
branch
from
October 8, 2026 16:06
cc4f2a3 to
08d8d0c
Compare
kaxil
approved these changes
Oct 8, 2026
ashb
force-pushed
the
task-loops-stack-7
branch
from
October 8, 2026 20:45
08d8d0c to
636464c
Compare
ashb
force-pushed
the
task-loops-stack-7
branch
from
October 9, 2026 10:32
636464c to
240027d
Compare
ashb
marked this pull request as ready for review
October 9, 2026 12:39
ashb
requested review from
XD-DENG,
bolkedebruin,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
potiuk
as code owners
October 9, 2026 12:39
ashb
force-pushed
the
task-loops-stack-7
branch
from
October 9, 2026 14:03
240027d to
cde2024
Compare
ashb
force-pushed
the
task-loops-stack-7
branch
from
October 9, 2026 16:28
cde2024 to
262afa3
Compare
ashb
force-pushed
the
task-loops-stack-7
branch
from
October 9, 2026 20:34
262afa3 to
81a80be
Compare
ashb
force-pushed
the
task-loops-stack-7
branch
2 times, most recently
from
October 9, 2026 22:18
8f9fe24 to
8f2f3b2
Compare
The scheduler, the API and the UI must never see every task of a loop finished while its next pass does not exist yet. If we recorded a continuing gate as successful and created the next pass afterwards, a crash between the two would leave recovery unable to tell an unfinished advancement from a completed decision. Gate completion and next-pass creation therefore happen in one transaction under the DagRun lock, which also stops a duplicate completion from advancing the loop twice. The continue-or-stop decision is a reserved XCom stored under the gate's attempt UUID. A retried gate starts without a decision, and a retired attempt cannot advance the loop. An invalid decision moves the gate attempt to retry or failed within the same request; rejecting the request instead would leave the attempt running with nobody to finish it. Gates use normal task dependencies and an explicit loop context. A barrier that waited for every body task would override trigger rules that allow early progress. Workers and dag.test supply the same coordinates, so decisions and previous-iteration reads reach the intended gate and data. Skipping downstream of a task from outside a loop skips every live pass. Skipping only one would let later passes run work the author meant to skip.
On an unversioned bundle, renaming a loop's gate mid-run re-pins the running gate attempt to a Dag version that no longer has its task. Its completion then looked up the loop through that task and the request failed with a 500, leaving the attempt running with nobody to finish it. Supporting the rename is out of scope; the attempt is failed instead, without retry, because a retry would hit the same missing task.
ashb
force-pushed
the
task-loops-stack-7
branch
from
October 10, 2026 07:05
8f2f3b2 to
c834724
Compare
This branch has not been deployed
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
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.
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.