Skip to content

Conversation

@gibsondan
Copy link
Member

@gibsondan gibsondan commented Jan 14, 2026

Previously, you had to filter the event log to type:RUN_FAILURE to get the reason the run failed. Now, the "Failure" button up top is clickable and shows that information if it has been set from the event log scan that the run page does.

How I Tested These Changes

Load a run with a run failure with a stack trace and without, with and without a step failure, with a step failure with and without a stack trace

Changelog

[ui] Failed runs now display more information about why the run failed when clicking on the Failure status on the run page.

@github-actions
Copy link

github-actions bot commented Jan 14, 2026

Deploy preview for dagit-core-storybook ready!

✅ Preview
https://dagit-core-storybook-ebt1tl6cj-elementl.vercel.app
https://showrunfailureevent.core-storybook.dagster-docs.io

Built with commit 4e7aad0.
This pull request is being automatically deployed with vercel-action

@gibsondan gibsondan force-pushed the showrunfailureevent branch from 6a3756f to c48d8cc Compare January 14, 2026 18:48
…the failure event

> Insert changelog entry or delete this section.
@gibsondan gibsondan force-pushed the showrunfailureevent branch from c48d8cc to 4e7aad0 Compare January 14, 2026 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants