shivaam opened a new pull request, #75534: URL: https://github.com/apache/airflow/pull/75534
The task lifecycle diagram on the Tasks page is one generated flowchart, about 10,000 px wide, with some twenty yes/no boxes. At page width it is hard to read, and every correction means regenerating a PNG and its checksum. As discussed in the #documentation Slack channel, this replaces it with four small Mermaid state diagrams written in the page, each with a short note: 1. an overview of every state; 2. deferred tasks, including the ways a trigger can end a task; 3. waiting for a person, or for a reschedule; 4. clearing a task, drawn as tries. The docs build already renders Mermaid to SVG at build time, so later fixes are a text edit. The generator script, its PNG, checksum and icons are removed. Two nearby sentences are corrected: `dag-run.rst` said clearing sets `max_tries` to 0, and `deferring.rst` named a `TaskFailureEvent` class that does not exist. Every arrow was checked against the code and against every path in the current flowchart. The paths not drawn are the scheduler repeating its usual checks after a retry or reschedule, which the text covers, and three paths the old drawing implied but Airflow cannot take. #### Before and after **Before**, the current flowchart, shrunk to fit:  **After**, the section from a local docs build:  This builds on #75428, which fixed the deferral paths in the current flowchart; those fixes are carried into the new diagrams. It also replaces the flowchart that #74520 corrects, so that change would no longer be needed. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 5.5) Generated-by: Claude Code (Opus 5.5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
