I'm running into a rather bizarre issue of an airflow hourly Dag missing a scheduled run every day.
This hourly dag is schedule for 0 * * * *, yet it does not generate a run for 0500 hours
I have another daily Dag that has a crossdag dependency to a task in that hourly dag. The daily dag is schedule for 0 5 * * *
I don't know what could cause Airflow to skip scheduling an entire run. My dags don't have any settings for concurrency or max_active_runs. Don't have task level concurrency limits either (pool, task_concurrency). Even if they are set, I believe these parameters would only queue the execution of dags or tasks, not skipping a schedule run entirely(maybe someone confirm)?
I'm guessing it would be something in the global Airflow settings that limits the number of active dag runs being scheduled at the same time. Any suggestion what it might be? The environment has been set up by our infrastructure team a long time ago so I would need to provide some instructions for them to take a look
Airflow version 1.10.12