title: Changing timezone triggers DAG's last execution again
body: <p>I have an issue managing the Timezones, I know that Airflow runs with UTC Timezone, I live in Santiago/Chile and I need the Dag's to work with the local time zone.</p>
  <p>In order to manage this I changed the timezone of my DAG like this:</p>
  <pre><code>timezon = &quot;Etc/GMT&quot; + Variable.get(&quot;timezoneVariable&quot;)
  chile_tz = pendulum.timezone(timezon)
  </code></pre>
  <p>The Variable timezoneVariable is set to &quot;+3&quot; in order to simulate our timezone.</p>
  <p>Then the DAG is configurated as it follows:</p>
  <pre><code>with DAG(
          dag_id = &quot;DAG_1&quot;,
          default_args = default_args,
          max_active_runs = 1,
          schedule_interval = &quot;0 14 * * 2,5&quot;, 
          start_date = datetime.datetime(2022,1,26, tzinfo=chile_tz),
          catchup = False
      ) as dag:
  </code></pre>
  <p>When I do this the schedule_interval gets hooked to the chilean timezone and not to UTC.</p>
  <p>The problem occurs when we change timezones for the daylight saving, the idea is that I don't have to change every DAG schedule interval, I only need to change the timezoneVariable from &quot;+3&quot; to &quot;+4&quot; and we are ready (I know that we can put Chile/Continental timezone for it to change automatically but we want to have the control in order to plan when we'll do the timezone change). When I changed the variable value from &quot;+3&quot; to &quot;+4&quot; it changed the timezone in every single DAG configured this way which is correct, but I also triggered again the last execution of every single DAG</p>
  <p>In my example case the DAG triggered normally on tuesday &quot;2022-03-29&quot; and friday &quot;2022-04-01&quot;, but on Sunday &quot;2022-04-03&quot; we did the timezone change and it triggered a new DAG execution with run execution &quot;2022-03-29&quot; (same value as the friday execution).</p>
  <p>Thanks!</p>
  <p>I want to know how can I avoid that every DAG triggers again the next time we change timezones.</p>
  <p>Thanks!</p>