A K8up job (backup, check, prune) has been queued without starting for a long time
In the namespace that is mentioned in the
message annotation (NOT the one mentioned in the
jobsthat could not be started/run
kubectl get backup,check,prune)
The alert will persist, even if subsequent jobs succeed. If subsequent jobs of the same type were successful, delete the problematic object to resolve the monitoring alert.