UMRA automation projects will show their error status in the UMRA task scheduler (View > Task Scheduler).
In most cases, you can right click on the script in question, and select View Log from the context menu. This will open the latest debug log file inside of your default text editor.
Searching for errors
Once you have the debug log file open, search for the string ": error" (minus quotes). This should find the latest first instance of an error in the automation script. An example of an error you might find is this:
My UMRA Script Line 1: Error finding AD account: Cannot convert NT4 style name 'Non_Existent_User@domain.local' to LDAP name.
Having a colon at the beginning of your search string is important, as simply searching for the word "error" will result in false positives. The word "error" is strewn throughout the debug log, and its presence does not necessarily denote a true error.
I didn't find an error in that file. Now what?
Using the View Log option from the context menu only opens the latest debug log. Debug log files in UMRA are cyclic, and their options are configurable in the service properties.
To see the other debug log files, you will need to go to the service's log directory. This is typically C:\Program Files (x86)\Tools4ever\UmraSvc\Log.
Once you've found the debug log directory, you can open one or more debug log files and search them for errors. We recommend using Notepad++ for its ability to open and search through numerous files.