SQLJobCommander:ReleaseNotes: Difference between revisions

Latest revision as of 21:37, 22 July 2026

Known Issues

Should a Job Monitor connection to an instance fail, the status of the SQL agent is not updated appropriately.
When creating or editing a job, the same schedule can be chosen more than once. However, on save, duplicate schedules are removed.
There is no immediate indication of an error should one happen while copying a job to another instance. However, the error is output to the session log.
The Success Rate metric shows NaN when it should show 0 (zero) when a success rate has not been established, i.e., no jobs have run.
If the Job Monitor grid is sorted by any column and the data is refreshed or the theme is changed, the column sort is reset.

@@ Line 6: / Line 6: @@
 * Initial release! Enjoy!
 * See what SQL Job Commander can do for you over in the [[SQLJobCommander:Documentation|documentation]].
+<span style="color:#FF1D44;font-weight:bold;font-size: 12px;text-transform: uppercase;">Known Issues</span>
+* Should a ''Job Monitor'' connection to an instance fail, the status of the SQL agent is not updated appropriately.
+* When creating or editing a job, the same schedule can be chosen more than once. However, on save, duplicate schedules are removed.
+* There is no immediate indication of an error should one happen while copying a job to another instance. However, the error is output to the session log.
+* The ''Success Rate'' metric shows ''NaN'' when it should show 0 (zero) when a success rate has not been established, i.e., no jobs have run.
+* If the ''Job Monitor'' grid is sorted by any column and the data is refreshed or the theme is changed, the column sort is reset.