Debugging automations

Debugging is an exercise to identify what went wrong in the execution of a scenario that resulted in unexpected behavior. This is a constant friend of any application built by anyone, and Honeycode is no exception to it. Debugging can be simple when you can see and test what was wrong, but is difficult when a scenario failed due to some external triggers beyond your control. For such cases, you need some information (logs) about the execution. For Honeycode automation, this information is available through the Run History button on the toolbar. An example of run history is shown in Figure 5.25:

Figure 5.25 – Run history of an automation

Another useful trick for debugging or temporarily disabling some of the automation blocks is to set the run condition to False(), in which case the entire block is skipped during execution, as shown in Figure 5.26:

Figure 5.26 – Debugging automation by temporarily disabling...