<h3 dir="auto">Apache Airflow version</h3>
<p dir="auto">2.2.0b2 (beta snapshot)</p>
<h3 dir="auto">Operating System</h3>
<p dir="auto">ubuntu 20.04</p>
<h3 dir="auto">Versions of Apache Airflow Providers</h3>
<p dir="auto">n/a</p>
<h3 dir="auto">Deployment</h3>
<p dir="auto">Virtualenv installation</p>
<h3 dir="auto">Deployment details</h3>
<p dir="auto">pip install /path/to/airflow/src</p>
<h3 dir="auto">What happened</h3>
<p dir="auto">Given any DAG initialized with: <code class="notranslate">schedule_interval=None</code></p>
<p dir="auto">Run <code class="notranslate">airflow dags test mydagname $(date +%Y-%m-%d)</code> and get an error:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="INFO - No run dates were found for the given dates and dag interval."><pre class="notranslate"><code class="notranslate">INFO - No run dates were found for the given dates and dag interval.
</code></pre></div>
<p dir="auto">This behavior changed in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="859407036" data-permission-text="Title is private" data-url="https://github.com/apache/airflow/issues/15397" data-hovercard-type="pull_request" data-hovercard-url="/apache/airflow/pull/15397/hovercard" href="https://github.com/apache/airflow/pull/15397">#15397</a>, it used to trigger a backfill dagrun at the given date.</p>
<h3 dir="auto">What you expected to happen</h3>
<p dir="auto">I expected a backfill dagrun with the given date, regardless of whether it fit into the <code class="notranslate">schedule_interval</code>.</p>
<p dir="auto">If AIP-39 made that an unrealistic expectation, then I'd hope for some way to define unscheduled dags which can still be tested from the command line (which, so far as I know, is the fastest way to iterate on a DAG.).</p>
<p dir="auto">As it is, I keep changing <code class="notranslate">schedule_interval</code> back and forth depending on whether I want to iterate via <code class="notranslate">astro dev start</code> (which tolerates <code class="notranslate">None</code> but does superfluous work if the dag is scheduled) or via <code class="notranslate">airflow dags test ...</code> (which doesn't tolerate <code class="notranslate">None</code>).</p>
<h3 dir="auto">How to reproduce</h3>
<p dir="auto">Initialize a DAG with: <code class="notranslate">schedule_interval=None</code> and run it via <code class="notranslate">airflow dags test mydagname $(date +%Y-%m-%d)</code></p>
<h3 dir="auto">Anything else</h3>
<p dir="auto"><em>No response</em></p>
<h3 dir="auto">Are you willing to submit PR?</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox"> Yes I am willing to submit a PR!</li>
</ul>
<h3 dir="auto">Code of Conduct</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I agree to follow this project's <a href="https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md">Code of Conduct</a></li>
</ul>
<p dir="auto">Running the scheduler used to spit out logs of information. It now spits out nothing other than the airflow header. Also, I am able to verify that when I put logging in <code class="notranslate">airflow_local_settings</code> that I get log messages output on the console.</p>
<p dir="auto">Using commit <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/apache/airflow/commit/edd0fd3411dba5f881cb11fe8a93d77cfafbcedf/hovercard" href="https://github.com/apache/airflow/commit/edd0fd3411dba5f881cb11fe8a93d77cfafbcedf"><tt>edd0fd3</tt></a></p>