The defined date range in iDash does not reflect correctly in the report

Products

• iDash Workload Automation

Issue/Introduction

We found that dates generated in run/status reports include previous dates. Is there a way to configure iDash to return ONLY dates within the date range they are reflected?

Resolution

After reviewing the code for this report, it looks like there is a reason these rows are being included. 

The job status report works a little differently from the job run report. In the run report, the Timeframe does indeed refer to the start and end time of the job run. However, in the job status report the Timeframe refers to the status time on the job, not the start and end time of a run. There are statuses available to report on that would not yet have start and end times, and selecting job statuses based on the job start and end time would exclude those job statuses from being displayed. So, instead the report uses the Timeframe parameters to select job statuses based on the status_time attribute of the job. 

In these cases, you are seeing jobs that have statuses that were updated within the Timeframe specified in the report, even though the start or end time of the job run is outside of the Timeframe. 

When auto-import of data for an Autosys instance is turned on in iDash, iDash will use its own DB to source the data for a job run report. The expectation is that iDash will always have an updated record of job runs and we can lessen the impact on the Autosys DB by running the query against our own DB. For the job status report, however, the report data is always sourced from the Autosys database. There are statuses a job may be in that do not result in a run record being created, and we only import runs. So, we must go to the Autosys DB to gather accurate status data. Cleaning up the iDash DB for runs will not do anything to job status records in the Autosys DB. 

The fact that the records in question appear in the report means that Autosys is updating the status for those jobs within the Timeframe you defined in the report. We can't say what is going on with those jobs in Autosys, only that the status_time was updated within the range corresponding to the report.