{kb-symptom}
Tasks whose execution time exceeds the configured reporting interval are not shown in future reporting runs.
\\
For example, if a report is configured to run every four hours, and a task runs for longer than four hours, the task will be shown in the first execution of the report, but not in subsequent executions when the task is still running or has failed.
{kb-cause}
This issue occurs because the query used for reporting is being executed based on the task start date & time, and only tasks that have started since the last report execution time are shown.
{kb-resolution}
The issue has been resolved in CDP 4.0.0. Additional checks are now being made so that tasks will also be displayed in the following conditions:
* The task is still running or queued.
* The state of the task has changed since the last report execution time.
\\
\\
{kb-related-articles}
Tasks whose execution time exceeds the configured reporting interval are not shown in future reporting runs.
\\
For example, if a report is configured to run every four hours, and a task runs for longer than four hours, the task will be shown in the first execution of the report, but not in subsequent executions when the task is still running or has failed.
{kb-cause}
This issue occurs because the query used for reporting is being executed based on the task start date & time, and only tasks that have started since the last report execution time are shown.
{kb-resolution}
The issue has been resolved in CDP 4.0.0. Additional checks are now being made so that tasks will also be displayed in the following conditions:
* The task is still running or queued.
* The state of the task has changed since the last report execution time.
\\
\\
{kb-related-articles}