We have had several occasions when a collection/publish schedule has neither failed nor completed, it just stays in the Pending state forever until someone notices the start date time of the schedule and raises a flag. In our situation this has run for over 10 days and by that time db maintenance has already cleaned up a lot of related processes and it becomes impossible to cancel or clear them, even the restart does not help.
It would be nice to get a notification when a schedule has run for more than let say 10 hrs, then we know something has happened and should be able to resolve in the early stages. Nothing complicated just something similar to the notification we get when a schedule fails or terminates.
Support
Documentation
Learning Services
Partner Programs
