Logs

When your flow encounters an error, it will try to recover and continue running. Some errors are recoverable (meaning the flow will log the error and keep running), and some are not (meaning the flow will stop when the error is encountered).

Logs Page

Whenever your bot (within flow execution or the Inventor Runtime) encounters an error, it is logged and sent to the Logs page. You can also use an Error block to emit a custom error, which will also be sent to the Logs page of the dashboard.

The Logs page lets you see the log, what caused it, and potential solutions. You can also see details of every occurrence of the log, and how many times it has occurred.

Log Types

There are a few classifications of logs within Inventor:

  • Info - Informational messages that aren't necessarily a problem, but are important to know about and may help in debugging other issues.
  • Warning - Warnings are issues that may cause problems, but are not necessarily fatal. They should be investigated and fixed, but they won't stop your flow from running.
  • Error - Errors are issues that will cause your flow to stop running. They should be investigated and fixed as soon as possible.
  • Realtime Log - This is a special system that allows you to create and view short, message-based errors in realtime. Realtime log entries can only be created through the Realtime Log block.

Inventor issues a wide range of logs, some for the runtime/platform and some for flows and blocks. Most block errors are classified as Error.

While the vast majority of standard logs are generated by Inventor, you can log your own errors with the Log Error block.

Resolve and Ignore Logs

Resolved

Once you've investigated a Log and fixed it, you can mark it as resolved. This will move it from the Unresolved tab to the Resolved tab.

If the same log happens again, it will create a new log in the Unresolved tab.

Ignored

If there is a log that keeps coming up, but that you can't solve or that isn't important, you can mark it as ignored. This will move it from the Unresolved tab to the Ignored tab.

If the same log happens again, it'll be grouped in with the ignored logs under the ignored tab. You can always un-ignore the log if you want to see future occurrences of it in the primary/unresolved tab.