When to Use AutomationCondition.on_cron() vs Jobs for Asset Orchestration

AutomationCondition.on_cron() is the recommended approach for most asset orchestration scenarios, especially when:

• Scheduling single assets or simple asset groups

• Working with asset-centric workflows

• Using Dagster 1.7+

• Requiring asset lineage and dependency tracking

• Needing built-in monitoring and freshness tracking

Jobs should be used when you need:

• Complex orchestration logic

• Conditional execution flows

• Mixed asset/op workflows

When using AutomationCondition.on_cron() for multiple assets:

• Assets execute independently in parallel

• Each asset runs in its own isolated container

• Resources automatically scale to handle concurrent executions

• No queuing occurs between different asset materializations

For comprehensive monitoring of asset executions, you can utilize:

• Asset sensors

• Asset checks

• Hooks