# Dagster 1.13.12 — 1.13.12 (core) / 0.29.12 (libraries)

- Product: Dagster (https://whatsnew.fyi/product/dagster)
- Vendor: Dagster Labs
- Date: 2026-07-02
- Version: 1.13.12
- Original notes: https://github.com/dagster-io/dagster/releases/tag/1.13.12
- Permalink: https://whatsnew.fyi/product/dagster/releases/1.13.12

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **changed** — 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
- **added** — 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
- **fixed** — 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** — 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** — 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** — Fixed a KeyError on failures when converting dbt run results to Dagster events for runs that omit that key

###### New

- [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](https://github.com/noy-solvin)!)

###### Bugfixes

- 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](https://github.com/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).