Error Logs and Notifications


Navigation:  Error Handling >

Error Logs and Notifications

You can use error notifications to warn when an agent encounters an error, so that the administrator can take appropriate action. The administrator can use the logs to get more information about the errors.


Error Notifications

Notifications are email messages that are sent to a specific email address when certain conditions occur. The notification configuration screen is available by clicking the Agent Settings > Notifications menu.



This agent sends email notifications if it encounters any

critical errors


An email notification can be sent when an agent finishes, but never during agent execution or when debugging an agent. You can choose to send email notifications when one or more of these conditions are met:



Always send notifications when an agent completes a run

A notification email will always be sent when the agent finishes, whether an error occurs or not.

Send notification on critical errors

An email notification will be sent when critical errors occur. A critical error will appear as red color on the log screen. These critical errors include page load errors and also situations where required web selections are missing from a web page.

Send notification on low number of page loads

A notification email will be sent when an agent loads less than the minimum number of pages that you specify in Low page number threshold. Page loads include all command actions, including content loaded asynchronously using AJAX and content changes triggered by synchronous JavaScript.


A script can trigger notifications by calling one of these methods on the script parameter object:



void Notify(bool alwaysNotify = true)

Triggers notification at the end of agent execution. If alwaysNotify is set to False, this method only triggers a notification if you configure the agent to Send notification on critical errors (see above).

void Notify(string message, bool alwaysNotify = false)

Triggers notification at the end of an agent execution, and adds a message to the notification email. If alwaysNotify is set to False, this method only triggers a notification if you configure the agent to Send notification on critical errors (see above).


Error Logs

Logging is off by default. If you want to save log information, you must first enable logging before you run an agent or debug it. Simply locate the Debug section in the Properties tab, and set the Debug Disabled property to True.


A Content Grabber agent send log data to a database table by default. The database table supports the log viewer in the Content Grabber editor, which you can access by clicking the View Log button in either the Run ribbon menu or the Debug ribbon menu.



The critical errors in this log are red in color


URL Column

The URL column in the Agent Debug Log window shows links to all web pages that the agent has processed, and you can double-click on any of these links to open the web page in your default browser. For any failures on data extraction, this is an easy way to open the web page and check if the web page layout is different from the expected layout.


NOTE: Double-clicking on a link to a sub-page only works if the website allows direct links into the sub-pages. Many websites don't allow direct links into sub-pages without going through other pages first. Read below to learn how to directly access the HTML for sub-pages.


HTML Column

If a website does not allow direct links into sub-pages, you can configure an agent to save the entire HTML of all processed pages. When you configure the agent to log all HTML, the HTML column will contain buttons that you can click to view the raw HTML in the Content Grabber HTML viewer. The raw HTML does not include style sheets and other support files that are necessary to render a complete web page properly, but it will often show you enough information to determine what is causing an error (such a CAPTCHA page).