<p dir="auto">I have a newly created daily dag and I have set it up yesterday (Jan. 25th), once it is loaded by airflow I can see it is run once (scheduled_2021-0124T00:00:00+00:00), and then I manually triggered it once just to see if it works and it did (manual_2021-01-25).</p>
<p dir="auto">Now time is 08:24 UTC Jan 26th. But I did not see any run for 01-25. I have used <code class="notranslate">airflow dags next-execution</code> and found out airflow is planning to execute the dag for 01-26 directly, possibly on 01-27 00:00 UTC. So it will skip 01-25 entirely.</p>
<p dir="auto">I am wondering why this behaviour? Is there any reason behind this?</p>
<p dir="auto"><a href="https://i.stack.imgur.com/SYbEf.png" rel="nofollow"><img src="https://camo.githubusercontent.com/0ab20bbae7e4c4238924352ce65d55fced7bf717c8216481a5a7e249cec7338c/68747470733a2f2f692e737461636b2e696d6775722e636f6d2f53596245662e706e67" alt="enter image description here" data-canonical-src="https://i.stack.imgur.com/SYbEf.png" style="max-width: 100%;"></a></p>
<p dir="auto"><strong>Apache Airflow version</strong>: 2.0.0</p>
<p dir="auto"><strong>Kubernetes version (if you are using kubernetes)</strong> (use <code class="notranslate">kubectl version</code>): N/A</p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: local/aws</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): Ubuntu 18.04.5 LTS</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): 5.4.0-1032-aws</li>
<li><strong>Install tools</strong>: pip</li>
<li><strong>Others</strong>:</li>
</ul>
<p dir="auto"><strong>What happened</strong>:<br>
I did a fresh Airflow 2.0.0 install. With this version, when I manually trigger a DAG, Airflow skips the next scheduled run.</p>

<p dir="auto"><strong>What you expected to happen</strong>:<br>
Manual runs do not interfere with the scheduled runs prior to Airflow 2.</p>

<p dir="auto"><strong>How to reproduce it</strong>:<br>
Create a simple hourly DAG. After enabling it and the initial run, run it manually. It shall skip the next hour. Below is an example, where the manual run with execution time of 08:17 causes the scheduled run with execution time of 08:00 to skip.<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/26160471/103457719-c7193480-4d12-11eb-82cb-42efaedc9ef4.png"><img src="https://user-images.githubusercontent.com/26160471/103457719-c7193480-4d12-11eb-82cb-42efaedc9ef4.png" alt="image" style="max-width: 100%;"></a></p>