Note that all these traces are saved within unique procedure file
"*.bky-muz" (or unique instrument configuration file "*.bky-ciz"). So
on problem detection, user may use this unique file to keep complete
trace of what happens. Possible trouble resolution becomes easier and
even may be driven by people with sufficient system knowledge without
needing to access the system itself - only with analyze from saved
traced.
Note also that during automatic execution (run tree), each
procedure file "*.bky-muz" is auto-saved (hopefully, because results
are
inside!), and this auto-save is done when procedure finishes as nominal
(without any error) or when some error occurs. So if during an
automatic execution a trouble appears, the understanding of what
happened is also possible. When an error happens during automatic
execution of a procedure, this procedure is aborted and doesn't try to
continue, but automatic execution continues with next procedure.