Dagster 1.13.12 release notes

Dagster 1.13.12

1.13.12Jul 2, 2026 · about 1 month ago

1.13.12 (core) / 0.29.12 (libraries)

Added 1

Added a dashboard_refresh_interval parameter to PipesEMRServerlessClient and increased its default so that Spark UI URLs are no longer invalidated prematurely during a run

Changed 1

Improved the performance of the runs feed for runs that target large numbers of assets and asset checks by fetching a bounded preview of the selection and loading the full lists on demand

Fixed 4

Fixed a bug where a partitioned asset check with its own automation condition could raise a CheckError and halt the entire automation tick when it was requested on a tick that did not materialize the asset it targets
Fixed a bug where a code location could be left stuck in an error state after a transient gRPC failure during refresh by making the gRPC server watcher periodically retry refresh for locations whose load error is a DagsterUserCodeUnreachableError
Fixed an issue where long pool names could overflow their container by truncating them and wrapping and scrolling the run pools dialog when there are many pools
Fixed a KeyError on failures when converting dbt run results to Dagster events for runs that omit that key

[ui] Improved the performance of the runs feed for runs that target large numbers of assets and asset checks. The feed now fetches a bounded preview of the selection and loads the full lists on demand.
[dagster-aws] Added a dashboard_refresh_interval parameter to PipesEMRServerlessClient and increased its default so that Spark UI URLs are no longer invalidated prematurely during a run. (Thanks, @noy-solvin!)

Fixed a bug where a partitioned asset check with its own automation condition could raise a CheckError and halt the entire automation tick when it was requested on a tick that did not materialize the asset it targets.
Fixed a bug where a code location could be left stuck in an error state after a transient gRPC failure during refresh (common during Kubernetes rolling deployments). The gRPC server watcher now periodically retries refresh for locations whose load error is a DagsterUserCodeUnreachableError. (Thanks, @jmoldow!)
[ui] Fixed an issue where long pool names could overflow their container; they are now truncated, and the run pools dialog wraps and scrolls when there are many pools.
[dagster-dbt] Fixed a KeyError on failures when converting dbt run results to Dagster events for runs that omit that key (such as dbt Fusion).