Yes. Dag versioning https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-36+DAG+Versioning is not yet implemented (or even designed completely) so changing dag id is recommended in this case.
As explained in https://airflow.apache.org/docs/apache-airflow/stable/index.html - this still holds as rather basic "feature" of Airflow (and applies also to schedules): Workflows are expected to be mostly static or slowly changing. You can think of the structure of the tasks in your workflow as slightly more dynamic than a database structure would be. Airflow workflows are expected to look similar from a run to the next, this allows for clarity around unit of work and continuity. On Wed, Jun 1, 2022 at 10:29 AM Konrad Dusza <[email protected]> wrote: > Hi, > > > > We changed interval and start_date (timezone) in a dag, and forgot to > rename it. > > We observer weird behaviour (next run date was not correct) but after > 24hrs from deployment it corrected itself. > > > > I remembered after the fact that it used to be recommended, that a change > in interval and/or start_date should be done along with dag rename (usually > adding a _v2 suffix, etc. to dag name). > > However, this practice is mentioned in a document > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62694614 > that is now marked as archived. > > I didn’t find any mention of this in official documentation. > > > > Please advise on the recommended course of action, we’re now facing a > reschedule (timezone changes) for 20+ dags and perhaps again in the future, > and would like to establish a process for that, that doesn’t result in some > hidden bugs or anything, but does not force anyone to rename dags if it > isn’t absolutely necessary > > > > -- > Konrad Dusza > > >
