Dick, as always thanks for your help.

Russ, "weather failure" is a Plan that is failed due to one of its Observations encountering an unsafe weather condition and terminating before it's completed. In that case the Plan will be rescheduled for the next night. Other failures, including "passing clouds" causing guiding or other failures, will not get automatically rescheduled. The Scheduler is not that smart. In the beginning I allowed auto-reschedule of any failure, but it quickly became evident that it was a bad idea. Most non-weather failures are equipment/USB/etc. failures and in that case the scheduler would fail Plan after Plan, rescheduling and failing again and again. Just last June, we had a situation where an equipment failure caused many Plans to be failed. After all these years, the idea came up of having the Scheduler just stop after "too many" failed Plans in a row. That one is on the queue.

SCHEDULER-1583 - Operator Intervention on "too many" ACP Observation Errors

The "passing clouds" problem is one that's difficult to address rationally. One customer created a constraint that was supposed to force the scheduler to shoot through "sucker holes" using a 10.6 micron IR all-sky camera and zonal analysis. It looked good on paper but didn't turn out to significantly improve productivity on nights with scattered to broken clouds.

With all that said, what caused your Plans to fail? You can see the ACP run log from the web schedule browser spreadsheet. Find your Project, within that the Plan that failed and see its list of Observations, open the Observation that failed and caused the Plan to fail. and you should see a link to the log. Read the log to see what specifically caused the Observation (and thus the Plan) to fail.