Hi
@Ben Fogelson, if you’ve got the state object in-memory already from running the flow interactively, these docs will help:
https://docs.prefect.io/core/advanced_tutorials/local-debugging.html#re-raising-execeptions-post-hoc
If you are using server or cloud so don’t have the state object handy, there’s not really a great way to hydrate it completely, but you might consider preventatively persisting the state of a flow as a cloudpickle via a flow-level state handler, which you could deserialize for debugging purposes using those same local debugging tips from those docs!