dg.AutomationCondition.on_cron("0 9 * * *") requests an asset once per cron tick, but only after every dependency has been updated since that tick. If the source refreshes at 9:20, the asset runs at the first evaluation after 9:20, not at 9:00 on stale data, and not again until the next 9:00.
Compared with a schedule, on_cron adds the dependency wait. Compared with eager, it caps the rebuilds at one per period, which matters for expensive models read once a day. A time zone is the second argument: on_cron("0 9 * * *", "Europe/Madrid").
On the tick list, each part of the condition shows whether it was true: whether a cron tick has passed since the asset was last handled, and whether all dependencies have updated since that cron tick.
Once a day, after 9:00 and after raw_orders has refreshed.