Hello,
we have the problem with various customers: When a job is currently running and you look under "Running", various other jobs are displayed, but they are not actively executed. Is there a way to hide these jobs here?
But if you then look at the job, you can see that the jobs have already been successfully completed. If there is no job running, running is not visible either. Even if the services are restarted, the entries under "Running" disappear. It suggests that this is a view problem. is there a workaund here?
the solution is quite simple: Press F5 in the window and it will refresh. This is a known issue that was first seen in V11 IIRC and it is purely cosmetic in nature. There were patches for it for V11 and V11a, but these did not solve the issue in all installations. I have not seen it in V12 myself, but there is already a thread in the forum describing this also occurring in V12.
This issue seems to still be persistent in v12 as well. Not sure if it is database related based on the one you are using - MSSQL or PostgreSQL but it is still there. Hopefully, they will address this in the next release.
I have a job from two days ago, on December 17th. During the job, the backup-storage device crashed while the job was at 85%.
Repaired the storage and the same job completed perfectly on the 18th and 19th. But the GUI still shows the job of the 17th at 85%. When I click on the job (view statistics), what is shown is the results of the job of the 19th (which finished normally).
When trying to stop the job, it asks me if i'm sure, I say yes, then it says that the job cannot be stopped because there is no job.
F5 does not help, nor does rebooting the backup server.
I can edit the job, for example changing the scheduled start-date slightly and after saving, it shows in the "Next Run" column with the new start-time. But the rest still shows running at 85% and last run was two days ago.
It's purely a display thing and it has no operational impact as the job runs fine every day.
