Potential WCC Reporting Delays and Historical Data Loss After Upgrading to AutoSys 24.0

Products

• Autosys Workload Automation

Issue/Introduction

After upgrading to AutoSys Workload Automation 24.0, Workload Control Center (WCC) reports may fail to generate or may appear to be stuck with the "Report collection" status continuously showing as "Running". This can prevent new data from appearing in reports for a period of time.

 

Environment

Product: AutoSys Workload Automation, Workload Control Center (WCC)

Product Release: Upgrade to 24.0

Cause

Once reporting functionality resumes, it may be discovered that historical job run data older than 30 days is no longer available. This occurs because the data purge setting in WCC, which may not have functioned correctly in previous releases, is now working as designed in version 24.0. The initial delay is possibly caused by the system purging a large volume of accumulated data that exceeds the retention period defined in the configuration.

Resolution

This is a suggested action to retain historical data and potentially mitigate reporting delays after an upgrade. The speculated cause is the newly-enforced data retention policy, and this solution extends that policy's timeframe. This suggestion has not been fully validated.

To prevent the loss of historical reporting data beyond the default 30-day window:

1. Log in to the Workload Control Center (WCC) UI.
2. Navigate to the Configuration tab.
3. From the left-hand menu, select View/Modify Preferences.
4. Expand the Reporting section.
5. Locate the Purge Data setting. This value represents the number of days to retain reporting data.
6. Increase the value to a desired number of days, for example, 365 to keep one year of data.
7. Click Commit to save the changes.

 

After these changes have been made, wait a bit and then try to run a new report to see if it is working now.