potiuk commented on issue #30615: URL: https://github.com/apache/airflow/issues/30615#issuecomment-1506934507
And - you need to check what's your configuraton for SCHEDULER @timecommunication . It's sometimes a mistake that people do, that they check the environment variables/config in a different place than where airflow components are running. Airflow is a disstributed system and If your deployment is (wrongly) configured to used different configuration/environment variables for different components, then you might see different values in webserver and your scheduler might see them differently. So check this. Also in case you already have dags created in the past with the same name and deleted them, adding new dag with the same id will bring it back to the UI but this is going to be THE SAME dag than previously used, so if it was paused before and then deleted - it will disappear from UI, but when you add ti, it will continue to be paused. "dag on creation" setting wil only work if you add NEW dag_id, not restore the old dag_id after it has been removed. Actually this is the most likely reason - your screenshot shows some past runs, so it is likely it has been restored, not created when you observed the "paused" status. Converting into discussion in case there is more to add. -- 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]
