The Automated Build Studio generates full-detail logs of macro runs. These logs help you isolate the errors that might arise during the macro execution.
By default, when Automated Build Studio is executing a macro, it shows the name of each operation being executed in the Log panel. If an operation has child operations, they are logged as child nodes of their parent operation’s node. If an operation fails to execute, the Automated Build Studio will log information about the error that occurred. As a result, you get a complete log of the macro run:
Automated Build Studio includes special operations that let you enable and disable logging during the run. You can also post messages to the log from scripts.
You can also track the macro execution using the Summary panel (see the figure below). The Summary panel shows the names of executed operations, their results and the start and end time of the execution. The panel automatically compares the results of the current macro run with the results of the last successful run and quickly finds out if something is going wrong:
The contents of the Summary panels can be exported to an HTML file for further analysis. The contents of the Log panel can be saved to an HTML, XML or a text file.