Dagster 1.13.27 - Duplicate Run Fix and Cheaper BigQuery Insights Queries


Dagster 1.13.27 (libraries 0.29.27) was published on 2026-10-26 as a stable release. The change with the most operational weight is a UI fix: run action menus now close after a selection, so repeated Re-execute clicks no longer create duplicate runs. The rest is a bounded BigQuery query, a Sling tweak, and a set of selection input fixes.

The full release notes and downloads are on the GitHub release page.

Symptom: a user clicks Re-execute while a launch is still in progress, and a second run appears. Trigger: the run action menu stayed open after an item was selected, so a second click was easy. Blast radius: duplicate runs against whatever the job writes to. The fix closes the menu on selection.

Two related run page changes are worth knowing about:

  • Failing backfills now show up when you filter the Runs page by Failed, and they count toward the Failed total. If you built alerts or dashboards by eyeballing that count, expect it to rise.
  • The delete run dialog no longer offers “Terminate instead” to users who lack permission to terminate the run.

There is also a new mobile layout for the run details page, showing tags, logs, and steps. That is UI only and does not touch the pipeline.

For dagster-cloud, BigQuery Insights cost queries now bound the INFORMATION_SCHEMA.JOBS scan to the time window of the dbt invocation. Before this, the query could scan up to 180 days of job history. On a busy project that is a lot of bytes billed just to attribute cost to one dbt run.

The tradeoff is simple. Cost attribution is limited to jobs inside the invocation window. Jobs that fall outside it are no longer picked up, which is the point of the change. The contribution came from @pathisaivarun.

In dagster-sling, Snowflake connections defined with connection_string now identify Dagster as the partner application. If application is already set, your value is kept. Check your Snowflake query history filters if you group traffic by application name, since new tagging will appear for connections that did not set it.

Several fixes target the selection inputs, including the Runs search. They matter if you query by dbt model names or owner emails.

  • Values containing @, -, or . are no longer dropped, so an email address or a dbt model name stays whole when committing and in autocomplete.
  • Queries that start with whitespace now suggest and apply correctly.
  • Inputs with emoji, or with spaces around commas, no longer commit a corrupted query.

Two more UI robustness fixes landed. Pages could fail to load, or emit repeated errors, when browser IndexedDB storage was unavailable or over quota. Cached data now falls back to memory. Selecting an asset from the asset graph jump search with the keyboard no longer crashes.

New Dagster+ organizations no longer start with a [Dagster Plus] Credit Limit Exceeded alert policy. Only [Dagster Plus] Run Exceeds 24 Hours is created by default. Existing organizations are not mentioned in the notes, so do not assume anything changes for them.

The docs gain a guide for deploying the Dagster+ Hybrid agent on Azure Container Apps.

The notes list no breaking changes or migration steps. Core is 1.13.27 and the libraries are 0.29.27, so pin them together. If you run dagster-cloud or dagster-sling, bump those packages to get the BigQuery and Snowflake changes. See the release page for the exact wording.