Viewing logs and understanding the information contained in them is an important part of building, testing, and monitoring Processes. Logs can help you research where a Process failed and why. However, for some errors you will need to refer to your system documentation for more information and suggested resolution. It is outside the scope of Boomi AtomSphere to provide documentation for all types of errors from every application.
Execution events are logged in two places, at the Process-level and at the individual Document-level. Both types of logs contain a chronological account of what happened during a given execution including the order in which steps were executed and their outcome, as well as any error messages. Process Logs record the overall execution for all Documents processed, whereas Document Logs record the execution of a single Document.
Errors can be logged to either type of log or both depending on the nature of the error. When errors, it is best practice to consult the Process Log first to try to identify where the error occurred, then look at the Document Logs for failed Documents for more information.
Important: Although logs are viewed centrally from the Manage Tab, the actual log information is stored locally with the Atom. Consequently, the Atom must be online to be able to view logs.
Process Logs
Process Logs record the overall execution for all Documents processed. To view the Process Log, find the desired execution result (perhaps a failed one) and click the 
Log link for that row. The Boomi AtomSphere platform will connect to the Atom and retrieve the log contents:
If the Process had an error (as this example shows), look for an entry near the bottom of the log marked as "SEVERE". This entry will contain a 
Details link to view the actual error message:
This is the information you will use to help diagnose the error and take corrective action, whether that is a Process configuration change, research bad data, investigate physical connection problems, etc. In the example above, there was an error connecting to an FTP site, probably due to a bad user name and/or password.
Note that each step in the Process that was executed will have a log entry. This means you can determine at which step the error occurred based on the last step that was logged.
Note: If your Process uses an Exception shape to generate a user-defined error message, it will show up in the log as a SEVERE entry with a link to view your custom error details.
Document Logs
Document Logs record the execution of a single Document. To view a Document Log, find the desired execution result (perhaps a failed one), then find the desired Document entry and click the icon for that row. The Boomi AtomSphere platform will connect to the Atom and retrieve the log contents. As with the Process Log, find the entry marked as "SEVERE" and click the Details link for more information. The Document Log contains execution results specific to that Document, such as Decision, Route, and other Component outcomes which can be beneficial in debugging or troubleshooting Processes.
Important: For enhanced performance, executions that retrieve 50 or more inbound Documents will only provide Document Logs for Documents that had errors.
This page
Other pages
Account
