RNHTTR opened a new issue, #54482:
URL: https://github.com/apache/airflow/issues/54482

   ### Apache Airflow version
   
   3.0.4
   
   ### If "Other Airflow 2 version" selected, which one?
   
   2.11
   
   ### What happened?
   
   The cron expression `* * */1 * 5` is reported in Airflow as "Every minute, 
only on Friday", when in reality the dag runs every day. 
   
   <img width="270" height="76" alt="Image" 
src="https://github.com/user-attachments/assets/447b7bad-4e4d-4d66-8d34-4be23b9dff01";
 />
   
   Per the [cron 
manpage](https://www.man7.org/linux/man-pages/man5/crontab.5.html):
   > Commands are executed by cron(8) when the 'minute', 'hour', and 'month of 
the year' fields match the current time, and at least one of the two 'day' 
fields ('day of month', or 'day of week') match the current time (see "Note" 
below).
   
   That is, since the day-of-month field and day-of-week fields are both 
populated and cron interprets these fields as **OR**, this dag runs every 
minute of every day, rather than every minute only on Fridays.
   
   ### What you think should happen instead?
   
   The UI should say that a dag with the schedule `* * */1 * 5` runs every 
minute, or a dag with the schedule `0 0 */1 * 5` runs every day at midnight 
instead of saying midnight on Friday.
   
   ### How to reproduce
   
   Create a dag whose schedule is `"`* * */1 * 5`"`. Hover over the schedule 
widget in the UI.
   
   ### Operating System
   
   n/a
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to