Hello Oxygen List The console output (transformation log) is overwhelming for many standard users. They won't know what to look for in the log and tend not to check it at all as soon as some kind of output is generated, thereby overlooking potentially grave omissions in the output. Is there a convenient way a) to save the transformation log to disk b) to evaluate it with certain rules? For instance, it would be great if after a PDF transformation we could implement an automated brief check of the log file for occurrences of the string "[ERROR]" or also some pattern for certain warnings. If that string is found in the log file, initiate some action, e.g. renaming the output PDF (e.g. by appending "_errors_in_log" to the file name). Many thanks in advance for any ideas Richard