You need to test a scheduled task to make sure it actually does what it's supposed to do - reliably, on time, and without errors. Testing helps yo catch problems before they affect real operations.

 

Reasons to test a scheduled task:

• Verify the task runs correctly. Confirms the report or command executes without errors. Example: A report that silently fails means no reports are happening. 

• Check triggers and timing. Ensure it starts at the right time (like at 5 pm every weekday). 

• Validate permissions. Confirms that the task has the correct user account and rights to perform actions (like running a report). 

• Debug scripts or commands. Testing helps you find and fix bugs or incorrect paths, especially if files or serves are moved or renamed. 

• Avoid unexpected results. Prevents unwanted side effects, like overwriting files, sending emails too often, or causing performance slowdowns. 

• Prove it works for others.  In team environments or audits, testing shows that automation is functional and reliable. 

 

 

Schedule Tasks is included in the 2025.05 release. It supports General Ledger. More reports will be added for other Connect applications in the future. 

 

Testing a scheduled task

1. Open Connect System Management > System Tools > Schedule Tasks. 

2. Click to select a report (from the pane on the left). 

3. Click .

 

 

 

4. Check if the expected results occurred (for example, a file was created, a report emailed). 

 

If the test is not successful, check

• if the Enable Processing checkbox is selected.

• the report definition shows the correct one.

• the scheduled task options are creating the task at the right time and in the right place. 

 

 

If you need more help, call customer support or submit a support ticket. 

 

Copyright © 2025 Caselle, Incorporated. All rights reserved.