pierrejeambrun commented on issue #49617: URL: https://github.com/apache/airflow/issues/49617#issuecomment-2829687101
That's because the dag were not modified to work with AF3, meaning that the DAG cannot be reparsed successfully, most likely because we didn't change `schedule_interval` to `schedule`. Once the required change are made for the Dag to be parsable again, the interval will be converted correctly to the new format and displayed properly. I don't think there is anything specific to be done there, and I would recommend closing the issue, as long as the user upgrade its dag to be AF3 compatible, this UI glitch will go away. What do you think Rahul ? -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org