Users can configure various settings to define how errors are handled when running scheduled reports. These settings include options to treat a report as an error if it takes longer than a specified time to run.
Users can configure various settings to define how errors are handled when running scheduled reports. These settings include options to treat a report as an error if it takes longer than a specified time to run, retry executing a schedule in case of errors, and check for blank reports. By carefully configuring these settings, users can customize the behavior of ATRS to suit their specific needs and ensure the smooth operation of their reporting processes.
Exception Handling Wizard
.png?width=688&height=504&name=ATRS%20Package%20Reports%20Exception%20Handling%20(1).png)
Step 1: You may either set the Treat as “error” if not completed in X minutes (and specify the amount of minutes) or use the Auto Calculate option to determine if a report takes longer than the specified amount of time to run, both of these options will treat the schedule as an error and follow the appropriate action.
If manually determining the error timing, please double-check the run time of the report in order to get the correct time estimate.
Step 2: Should an error occur determine how many time the schedule should retry and at what frequency. Using the On error, retry executing schedule every. If set to 0, ATRS will deem the schedule as "Failed" the first time it encounters an error. The schedule will not run again until its next scheduled time. Change the value to tell ATRS how many times you want it to retry running the report before declaring it as "Failed."
Step 3: Users can also Run Custom Tasks when certain exceptions occur such as Blank Reports and decide on the appropriate action if ATRS comes across one.
Step 4: Check if the Report is Blank: If a report is blank because it genuinely returned no data, recipients can misconstrue this as an error with the scheduler. This option allows you to identify genuine empty reports and instruct ATRS on what to do with them.
Step 5: Ignore the report and subsequent tasks: If the report is blank, do not send the report. The report will not be delivered to the destination. No custom tasks will be run.
There are two ways to determine if a Report is blank. You may use a File Size Check or a SQL Query.
Method
/Blank%20report%20check%20method%20_%20file%20size%20check.png?width=609&height=351&name=Blank%20report%20check%20method%20_%20file%20size%20check.png)
- Select the Method that will determine whether a report is blank.
/Blank%20report%20check%20method%20_%20sql%20query.png?width=609&height=348&name=Blank%20report%20check%20method%20_%20sql%20query.png)
- SQL Query: Select this option to use a user made query that will determine if the report is blank. If the query returns no results, the report is blank.
- Click Build.
- Get values from a database window will appear.
/Get%20values%20from%20databaes%201.png?width=659&height=651&name=Get%20values%20from%20databaes%201.png)
Step 6:If the the report is blank you may choose to run a Task or a number of Tasks. or you may choose to check the option following option:
If the "Ignore the report and subsequent tasks" is selected, then the report will not be delivered to the destination. No custom tasks will be run. Conversely if you leave this option unchecked the report will be executed and so too will any custom tasks you set up.
Actions
/Actions%20window.png?width=687&height=286&name=Actions%20window.png)
Tip: You can send a notification if a report is considered blank instead of sending the report. Simply select “check if a report is blank” then select “Ignore the report.” In the actions tab, select “Send Email” from the list. Compose your email and save.