[YAshhh29]

While I was tracing the task lifecycle, I noticed that the branches after
"Required upstream task(s) failed?" are reversed in the diagram.

A YES answer currently continues through the normal scheduling checks,
while NO leads to upstream_failed. It should be the other way around:
when a required upstream task has failed, the current task moves to
upstream_failed; otherwise, the Scheduler continues evaluating it.

This PR swaps those two labels and regenerates the PNG and its source
checksum.

Validation:

• prek run generate-airflow-diagrams --files airflow-core/docs/img/diagram_task_lifecycle.py
• prek run ruff --files airflow-core/docs/img/diagram_task_lifecycle.py
• prek run --from-ref upstream/main --stage manual

---

Was generative AI tooling used to co-author this PR?

• Yes - GitHub Copilot

The PNG was regenerated deterministically from the diagram source using Airflow's Graphviz hook.

[uros-b]

Thank you @YAshhh29!

[potiuk]

Hello @YAshhh29 - thank you for your contributions to Apache Airflow!

The Airflow community has introduced a limit of 5 open pull requests at a time for contributors without write access to the repository. You currently have 6 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:

• Make Vertex AI evaluation stack an opt-in provider extra #69385 - Make Vertex AI evaluation stack an opt-in provider extra
• Add QdrantSearchOperator for vector similarity search #69673 - Add QdrantSearchOperator for vector similarity search
• Make generated AIP playbooks portable and verifiable #70477 - Make generated AIP playbooks portable and verifiable
• Fix upstream failure branch in task lifecycle diagram #71101 - Fix upstream failure branch in task lifecycle diagram

These pull requests stay open because maintainers are already engaged in them - they count towards your limit:

• Support Pydantic structured outputs in OpenAIResponseOperator #69812 - Support Pydantic structured outputs in OpenAIResponseOperator
• Fingerprint durable agent steps that hold sets or values that are not JSON #71575 - Do not replay cached AI steps that cannot be verified

This is not a judgement of you or of your changes. We never told contributors before that opening many pull requests at once was a problem, so there is nothing to feel bad about - and nothing is lost: your branches, commits and the review history stay where they are.

What we ask you to do is to make your first prioritization decision: choose which of the pull requests above matter most to you, and reopen them (up to 5 open at a time, including the ones still open) with the "Reopen pull request" button or gh pr reopen <PR_NUMBER> --repo apache/airflow. Reopen the ones you are ready to follow through - keep them rebased, respond to review comments and fix failing checks.

While your pull requests are waiting for review, the most valuable thing you can do is help in other ways - reviewing other contributors' pull requests, helping with issues, and taking part in the discussions on the devlist and Slack.

Why we introduced the limit, what it means for you and how to reopen or restore a pull request is explained in https://github.com/apache/airflow/blob/main/contributing-docs/32_open_pull_request_limit.rst.

---

Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting