|
Type:
|
New Feature
|
|
Priority:
|
High
|
|
Severity:
|
Minor
|
|
Status:
|
Closed
|
|
Resolution:
|
Complete
|
|
Resources:
|
Bob Denny
|
|
Reported By:
|
Bob Denny
|
|
Component:
|
Dispatch Scheduler Engine
|
|
Versions Affected:
|
8.3
|
|
Start Date:
|
7/12/2021
|
| Created: |
3/26/2018 5:19:05 PM |
| Revised: |
10/28/2021 11:24:26 AM
|
| Closed: |
10/28/2021 11:24:10 AM |
| Resolved: |
10/28/2021 11:24:16 AM |
|
See this Comm Center thread by Steve Reilly. Sometimes his rotator just disconnects, and the effect is that ACP fails every Observation thereafter. The effect is to fail possibly every Observation that might otherwise run in a night!
Add a new setting "max consecutive failures" and put the scheduler into Operator Intervention state if that number of consecutive failures is exceeded.
|
|
|
Links |
|
SCHEDULER-1772
|
|
Excessive ACP Errors -> Operator Intervention
|
Duplicate
|
|
SCHEDULER-1778
|
|
Handle 100% Plan failures
|
Related
|
|
ACP-1571
|
|
Support for Lunatico Good Night System
|
Grouped
|
|
|
|
|
|
|
|
|
Are you sure that you want to reset the votes?
