Seeing a weird problem where when running a dag on cron schedule 0 5 1,3-31 * * <http://airflowetl.ucera.local:8080/admin/dagrun/?flt2_dag_id_equals=hph_clarity_etl_trigger>
(note I am still using UTC time (since I do not believe that I can change it in v1.10.7)) that ends by running a TriggerDagRunOperator task. When the "triggering" dag runs, the Last Run date shows the correct date and is reflected in the run_id. Eg. 2020-03-04 05:00 <http://airflowetl.ucera.local:8080/admin/airflow/graph?dag_id=hph_clarity_etl_trigger&execution_date=2020-03-04+05%3A00%3A00%2B00%3A00> However, the dag that gets triggered shows the Last Run date as 1 day ahead and this unexpected behavior is also reflected in the triggered dag's run_id 2020-03-05 05:00 <http://airflowetl.ucera.local:8080/admin/airflow/graph?dag_id=hph_clarity_etl&execution_date=2020-03-05+05%3A00%3A47.975014%2B00%3A00> yet the triggering dag only takes about 1min. to run. Does anyone know what could be happening here? Is there a time difference that I am not recognizing here (note that I am not living in a UTC time zone (I am in HST and the cron is intended to run the triggering dag at 7:00PM each night excluding the 1st of each month))? -- This electronic message is intended only for the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you.
