# Agent Scheduler Cron and Workflow Runs
Status: public
Confidence: medium (0.725) (verified)
Last verified: 2026-06-02
Generation: ai_structured


## TL;DR

Scheduler definitions and workflow run history tell agents whether an expected job was configured, triggered, skipped, retried, or failed.

## Core Explanation

Agents investigating missing reports, stale indexes, late backfills, or absent notifications should inspect scheduler configuration and run history. Cron expressions, workflow events, DAG state, and recent run logs are often the fastest path to root cause.

The agent should distinguish planned schedules from actual runs. A correct cron expression does not prove the worker had capacity, credentials, or permission to finish the job.

## Source-Mapped Facts

- Kubernetes CronJob documentation says a CronJob creates Jobs on a repeating schedule. ([source](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/))
- GitHub Actions documentation says the schedule event can trigger a workflow at a scheduled time using POSIX cron syntax. ([source](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#schedule))
- Airflow DAG documentation describes DAGs as collections of tasks organized with dependencies and schedules. ([source](https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/dags.html))

## Further Reading

- [Kubernetes CronJob](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/)
- [GitHub Actions Scheduled Events](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#schedule)
- [Apache Airflow DAGs](https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/dags.html)