02-03-2013 05:10 PM
Hi,
Is there a way to stop the manualy canceled job showing up as failed job?
We have a successful job that is now overshadowed by red cross, rather then green tick.
I guess I just want to remove the extra over head labour.
Ta
Solved! Go to Solution.
02-06-2013 07:55 PM
Great suggestion except that I can not edit the job if it's on hold.
Will have to cope with it till the new version comes out.
Regards
02-03-2013 05:44 PM
No. A cancelled job will always show up as failed.
02-03-2013 08:56 PM
Thanks for that.
Do you know if Symantec is going to reclasify this as not failed?
Technically speaking it's not a failed job.
02-03-2013 09:47 PM
I don't think this is going to happen.
Technically it is a failed job, because it is not successfully completed.
02-03-2013 10:08 PM
In that case is there a way of cancelling a job before it runs?
I'm Not trying to debate it, just trying to understand the thinking and reasoning behind categorising what is failed and what is not.
Perhaps with the introduction of obvious job cancellation option before the job starts, I could not agree with you more.
Regards
02-04-2013 01:14 AM
If I am not mistaken, what you are looking for is to skip the next run in the schedule. Unfortunately, this feature was removed in BE 2012. If this is what you need, vote for my Idea below
https://www-secure.symantec.com/connect/ideas/bring-back-skip-next-run
02-04-2013 09:36 AM
Great suggestion in bringing back the Skip the next run PKH.. BEI in the mean time you can place the job on hold until you are ready for it to continue running according to its schedule.
02-06-2013 07:55 PM
Great suggestion except that I can not edit the job if it's on hold.
Will have to cope with it till the new version comes out.
Regards