In the last few chapters, we learned how to build new workflows and improve them. What we haven't covered yet is how we can catch errors and deal with them. By using presentation properties, we have already learned how to reduce the amount of errors by introducing a method that can be used to limit the user's possibilities to enter wrong values. Now, we need to have a look at how we deal with "real" errors, such as what happens if the new VM can't be built because there isn't enough disk space on the datastore.
Logs help us keep track of what's happening in the workflow as well as the settings.
We will also have a look at the debug modus of Orchestrator and learn how we can use it to test our workflows.