there are various occasions, where the pscheduler daemon would be unable to schedule a runs for a task, based on whatever temporary conditions. At this point pScheduler is setting "non-starter" tasks in the next 24h (by default).
It would be of great benefit, if the meshconfig as a service, which takes care of the automated mesh tests to review and identify such runs and try to remedy the failure states of the tasks. Possibly the review process will occur per hour.
AFAIK Meshconfig already does a similar review for the powstream tasks with keeping them always on the run and preventing excessive runs.
there are various occasions, where the pscheduler daemon would be unable to schedule a runs for a task, based on whatever temporary conditions. At this point pScheduler is setting "non-starter" tasks in the next 24h (by default). It would be of great benefit, if the meshconfig as a service, which takes care of the automated mesh tests to review and identify such runs and try to remedy the failure states of the tasks. Possibly the review process will occur per hour.
AFAIK Meshconfig already does a similar review for the powstream tasks with keeping them always on the run and preventing excessive runs.