dstandish commented on code in PR #25410:
URL: https://github.com/apache/airflow/pull/25410#discussion_r940772046


##########
docs/apache-airflow/faq.rst:
##########
@@ -41,13 +41,13 @@ There are very many reasons why your task might not be 
getting scheduled. Here a
   "airflow" and "DAG" in order to prevent the DagBag parsing from importing 
all python
   files collocated with user's DAGs.
 
-- Is your ``start_date`` set properly? The Airflow scheduler triggers the
-  task soon after the ``start_date + schedule_interval`` is passed.
+- Is your ``start_date`` set properly? The Airflow scheduler won't trigger the 
task until the
+  after the first schedule interval following the start date has passed.

Review Comment:
   reworded to clarify context



##########
newsfragments/25410.significant.rst:
##########
@@ -0,0 +1,3 @@
+Deprecation of ``schedule_interval`` and ``timetable`` params
+
+We add new DAG parameter ``schedule`` that can accept a cron expression, 
timedelta object, *timetable* object, or list of dataset objects. Params 
``schedule_interval`` and ``timetable`` are  deprecated.

Review Comment:
   done



-- 
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]

Reply via email to