Currently, any Jinja rendering errors will hard fail the workflow, preventing any error-handling steps within that workflow from firing. Allowing workflows to monitor their own success or failure and provide detailed error logging from within the workflow execution context would allow for significantly improved troubleshooting and error tracking. For example, perhaps a workflow leverages a custom API call and the API changes its object schema. The Jinja parsing the output fails, hard failing the workflow, which is configured to create a ticket if it encounters problems. However, because there was a Jinja rendering error, the workflow silently fails and no ticket is created.