Dagster 1.13.27 adds mobile run details and fixes duplicate re-execution

Run details become easier to inspect from a phone

Dagster released 1.13.27 on October 26, 2026, adding a mobile run-details layout with run information, logs and steps. Teams operating data pipelines and automated reports gain another way to inspect a run away from a desktop. The release also fixes an action menu that could create duplicate re-executions while a launch was pending.

Update a test environment and review re-execution before applying the change to jobs with external writes. This October 27 report does not equate a UI fix with exactly-once business processing; they are different layers.

Separate access to details, logs and steps

A run contains steps and events. Desktop layouts can display multiple panes for timing and logs, whereas a phone needs another arrangement. The 1.13.27 changes move run information into Details and provide dedicated mobile access to logs and steps.

The application distinguishes a mobile device from a narrow desktop window, rather than relying only on viewport width. Shrinking a desktop browser may therefore retain the desktop layout. A phone requesting the desktop site can also behave differently; record the actual device or emulation mode.

For on-call work, identify the failed job, step, message and run ID before acting. Do not re-execute everything merely because a result is hard to find. A run ID helps distinguish current logs from a previous attempt.

Repeated clicks could launch additional runs

The maintainer describes menus remaining open after an action was selected. Repeated Re-execute clicks during launch could create duplicate runs. Version 1.13.27 fixes that behavior, which matters when jobs send notifications or write into other systems.

The fixed button does not replace idempotency at the destination API. For example, a document-transfer workflow may need a stable request key or business lock to recognize completed work. That is Friday Works’ integration recommendation, not a claim that Dagster implements every accounting reconciliation rule.

After upgrade, test re-execution on a job without external effects. Observe menu state, pending launch and run counts. Do not use a live invoice or payment workflow for repeated-click testing.

A small, real run with synthetic input

Friday Works ran Dagster and dagster-webserver 1.13.27 in an isolated environment. A two-step job read three synthetic values and produced a total of 390000 VND. These are test data, not customer revenue or a measured business outcome.

Desktop captures show the actual successful run, steps and logs. Mobile-web captures use phone browser emulation, not physical-device or Safari testing. The trial validates the normal run and relevant screens; it does not reproduce the earlier click race or every failure condition.

For production, check compatible Dagster package versions, retain configuration and metadata, and follow the installation’s deployment process. A two-step demo cannot establish compatibility of a large reporting system.

Browser storage and BigQuery changes have separate scope

The release also falls back to in-memory caching when browser IndexedDB is unavailable or over quota. IndexedDB is browser storage; this cache fallback does not imply moving or deleting server-side results.

In Dagster Cloud, BigQuery Insights cost queries now bound the INFORMATION_SCHEMA.JOBS scan to the dbt invocation window instead of up to 180 days of history. This is a cloud integration change, not functionality exercised in the photographed OSS instance. No measured savings percentage is claimed.

Friday Works recommends reviewing log permissions, sensitive data visible on phones, re-execution confirmation and destination-system outcomes. Better mobile access helps observation when appropriately authorized; it does not automatically solve access governance or end-to-end workflow correctness.