Error handlers are a best practice for a smooth execution when writing Rundeck jobs. They allow you to gracefully account for more scenarios and conditions, as well as clean up the environment if a job fails. This session will focus on two examples of a failed job to show how error handlers work.
By the end of this session, you’ll know how to:
*Clean up after a failure
*Prevent job failure by waiting for required conditions, such as a file
Job Level: Intermediate
Job Role: Writer