Werk #22291: Veeam jobs: Do not report a job awaiting its first run as UNKNOWN
| Component | Checks & agents | ||||||||
| Title | Veeam jobs: Do not report a job awaiting its first run as UNKNOWN | ||||||||
| Date | Aug 28, 2026 | ||||||||
| Level | Trivial Change | ||||||||
| Class | Bug Fix | ||||||||
| Compatibility | Incompatible - Manual interaction might be required | ||||||||
| Checkmk versions & editions |
|
A Veeam job that has been created and scheduled but never executed was reported as UNKNOWN by the {{VEEAM Job}} service.
UNKNOWN is meant to indicate that the state of a job could not be determined. That is not the case here: the job exists and was queried successfully, it simply has no execution history yet.
Starting with this patch, a job that reports no result and is not running is OK, regardless of its job type. UNKNOWN is now reserved for a job state or result that the check cannot interpret.
Note: this changes the state of affected services from UNKNOWN to OK without any configuration change. Therefore this patch is considered incompatible.