In a @run_failure_sensor context, is there a way to get the original stack trace of the exception? This below just indicates the name of the step that failed.

context.failure_event.message

@yuhan - do you know the answer to this?

context.failure_event.event_specific_data.error

provides info about the error details

That returns None when I print it out

Do you mind sharing the error info shown in the run’s logs? Sensors operate outside the job execution process. That error field is a serialized exception representation that was extracted from the original exception with a custom serialization helper and stored into event db, which may not capture all info for some exception type.

In the UI, it shows up with EVENT TYPE = "STEP_FAILURE" with INFO below: dagster.core.errors.DagsterExecutionStepExecutionError: Error occurred while executing op "op_publish_to_snowflake": The above exception was caused by the following exception: Exception: test Exception Stack Trace: File "C:\Users\<RETRACTED>\Envs\khde\lib\site-packages\dagster\core\execution\plan\utils.py", line 47, in solid_execution_error_boundary yield , File "C:\Users\<RETRACTED>\Envs\khde\lib\site-packages\dagster\utils\__init__.py", line 387, in iterate_with_context next_output = next(iterator) , File "C:\Users\<RETRACTED>\PycharmProjects\khc_data_eng_core\python_lib\khde\khde\dagster\dagster_op_utils.py", line 206, in op_publish_to_snowflake raise Exception("test Exception")

Thank you! I'll try repro on my end. My hunch is we may not be storing stack trace into the db so probably will need to add that in the persistence layer.

so I'm assuming this would capture all scenarios:

error = context.failure_event.event_specific_data.error
if not error:
    event_logs = context.instance.all_logs(
        run_id=run_id,
        of_type=DagsterEventType.STEP_FAILURE,
    ) or []
    error = '<br><br>'.join([e.message for e in event_logs])

I believe so!

It looks like this implementation is no longer returning the stack trace - has something changed with ".message" attribute for step failure event logs?

Did a quick grep in the codebase. I don’t see any obvious change recently. Which version were you on and which version are you currently using?

currently on version 0.14.3

Hi! Sorry this thread slipped through my support tracking. looking now

yeah that provided the same error, I had to drill down but was able to find it:

step_failure_event_logs = (
    context.instance.all_logs(
        run_id=run_id,
        of_type=DagsterEventType.STEP_FAILURE,
    )
    or []
)
if step_failure_event_logs:
    errors = '<br><br>'.join(
        [
            str(e.dagster_event.event_specific_data.error)
            for e in step_failure_event_logs[:NUMBER_OF_ERRORS]
        ]
    )
if not errors:
    errors = str(context.failure_event.event_specific_data.error)

but just want to know if you know why the behavior changed and also confirmation that above would capture all the scenarios

that should capture all the scenarios. the reason why the behavior changed was we were double logging the same info in both user_message and message properties which caused unnecessary storage. so the change removed the redundant info, which should still allow you to get the same info but through a user_message.

Question in the thread has been surfaced to GitHub Discussions for future discoverability: https://github.com/dagster-io/dagster/discussions/8428