Details
-
Fix
-
Status: Known Issue (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
1.13
-
None
-
None
Description
Current Behavior:
When we create a job and disable the history parameter of that job, it is not generating history in jobs view but task history is created in the history view and when we try to access the log file it throws the exception as:
- 420 Error! DBMissingDataException: Task log with id 1376048 is missing
How to Reproduce:
- Create a Job with script and switch to the Options tab of the job
- Disable history parameter by giving it value as no.
- Run this Job and view task history.
- Switch to History view and when we try to access the log file it throws the exception as:
- 420 Error! DBMissingDataException: Task log with id 1376048 is missing
Desired Behavior:
If the history parameter is disabled, then no Job log should appear in the history view.
Maintainer Notes
- Understandably users would like any traces of job execution to be removed from task history.
- At the same time a number of recent changes, for example better notification support in case that jobs run longer or shorter than expected, are in conflict with this requirement.
- We therefore consider it acceptable to have a task history entry for the job execution, the task log definitely is not added to the database. Users are offered to add the respective job to the "Ignore List" that is available from the Task History view. This is a useful feature in case of frequently repeated jobs that tend to make it harder to read the history.
- As a general rule and in response to compliance requirements branch 2 of JobScheduler, the JS7, will not allow to suppress entries to the task history. Instead use of the "Ignore List" is recommended.