Concurrent asset materializations waste resources and cause dbt run failures

Assets are materialized multiple times concurrently when triggered by different sources (schedules, auto-materialize policies, or manual runs). This occurs even when the asset's data version hasn't changed or the asset is still fresh according to freshness policy. For dbt assets, concurrent materializations cause run failures.

Implement concurrency controls to skip asset materialization when another materialization is already in progress for that asset. Review auto-materialize policy configuration to avoid overlapping eager and lazy policies targeting the same asset subsets. Monitor dagster.asset.materialization for duplicate materializations within overlapping time windows and dagster.run.failed for dbt-related concurrent execution failures.