Summary
The user is working on a project using a FlyteRemote connection to retrieve information about failed executions for assessing failure reasons and relaunching executions in bulk. They want to programmatically access detailed error logs related to execution failures. The FlyteWorkflowExecution objects from remote.recent_executions() provide a truncated error message (limited to 100 characters), and the user is seeking a way to access the full error log from failed executions or alternative methods to obtain or set failure reasons, noting that the full error log is visible in the Flyte UI.