parkhojeong opened a new pull request, #66552:
URL: https://github.com/apache/airflow/pull/66552
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
#66462 The issue is that a paused Dag can show Next Run in the past, making
it look stuck or broken even though it is only paused.
<!--
<img width="1184" height="249" alt="image"
src="https://github.com/user-attachments/assets/d9efb1cb-a257-41c9-8fdf-411a5c688f78";
/>
-->
<img width="593" height="126" alt="image"
src="https://github.com/user-attachments/assets/49fa5a70-657a-437b-b516-2cf7a23da2cd";
/>
## Cause
The UI still renders Next Run for paused Dags, which can surface a past
timestamp and make the Dag look stuck.
Example:
- Current time: 10:03
- Dag state: paused
- Next Run: 10:02
## Fix
The fix updates the UI to stop rendering Next Run for paused Dags.
Changed areas:
- Dag list: card view, table view
- Dag detail: header
Dag list card view
<img width="1307" height="198" alt="image"
src="https://github.com/user-attachments/assets/1d9cda31-cb80-4b31-a420-0ee589da0766";
/>
Dag list table view
<img width="1306" height="206" alt="image"
src="https://github.com/user-attachments/assets/93b4f484-effd-4f3a-88d7-898424ab1dac";
/>
Dag detail header
<img width="1028" height="122" alt="image"
src="https://github.com/user-attachments/assets/98dba17b-751b-4df5-886d-8b5054d06830";
/>
<details>
<summary> repro.py </summary>
```py
import pendulum
from airflow.sdk import DAG, task
with DAG(
dag_id="repro_paused_next_run_drift",
start_date=pendulum.datetime(2026, 1, 1, tz="UTC"),
schedule="*/2 * * * *",
catchup=False,
tags=["repro"],
):
@task
def noop():
print("ok")
noop()
```
</details>
* closes: #66462
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
