Scheduler issues

hi Sorry to ask this again, but would people be so kind & sign up to the following two enhancement requests please.

We asked for an mail to be sent if scheduler fails. Pegasus have interpreted this if the task sets off & fails as it cant obtain exclusive access. Whilst this is helpful, it isnt what we meant

What we find quite a lot of the time, is we dial onto a server to grab a backup for some data investigation & we notice the last time scheduler backed up was say July! Services are al running & if you create a new task for copmany Z, it sets off. Its like for whatever reason it just decides to stop working. When we relay this to the clents, they interpret this that they havent had a bakcup etc & see it worse that what it actually is.

It would be great if somehow when a task doesnt even set off, an email is sent through with more clarification as to why/some sort of detailed audit log.

the KB's are 2105568, 2114854

Many thanks

James

Find more posts tagged with

Pegasus - Partner General Discussions

Accepted answers

All comments

conleth-overton

Hi James,

we are all signed up for both of these.

But they released scheduler 2.20.40 :-

A system generated e-mail can now be configured to send a system generated alert
e-mail when a scheduled task has failed to complete.

For Chained tasks, the e-mail notification will be for the entire chain (all the tasks in the chain) as the Scheduler
treats a chain of tasks as a single event and therefore records the history of the entire
chain. This functionality is also available for scheduled Data Intense Process (DIPs)
items in the Server Edition of Opera 3.
The e-mail notification includes information about the task, including the name, type
and when it started and finished. The end of the log file or the full log file will also be
included, but this is dependent on customer configuration.

hope this helps

unknown

Thats correct, it will send an email out if the task SETS OFF & then fails, as it cant say obtain exclusive access. (we have upgradd most of these problem sites to Opera 2.74 & 2.20.40 scheduler) But in these more common instances, the task doesn’t even set off. Theres nothing in event viewer & if you look at the history within scheduler, in the attached example the last record was 14/11/20. It has just all of a sudden decided to not even set off. Its this sort of notification were after so we can immediately dial on to see if theres any indication as to why. As in a mor technical notification, as opposed to one for an end user day their NL period end failed as someone was logged in Opera.

The second enhancement is for a better audit log to detail the “why” part. There is literally no evidence as to why scheduler has all of a sudden stopped. Were asked to start procmon & send an audit file in, check event viewer etc. Weeks can go by with no progress & it would be great if there was some method that revealed why & where the issue is.

Thanks for signing up though

Regards

James

claire-craig

done :-)

unknown

many thanks

Copyright © 2025 Infor. All rights reserved.