Understand Smart Patch Advisories

Not every update is safe the day it ships. Before you approve one, octoja shows you what is already known about it: Known issues collects advisories published about that KB, and Community reports shows you what other octoja partners are doing with the same update. Both appear on the update's detail page in the update catalog, so the decision to roll out, wait, or block happens where you make it.

Where the advisories come from

Both panels carry a badge that tells you how firm the finding is — for example Confirmed for a vendor-acknowledged issue, or Critical for a report of severe impact. The number next to the panel title is how many entries exist for this update. Links open the underlying advisory or article so you can judge the source yourself.

The daily collection may lag behind public reports and does not cover every report. An empty panel is not proof that an update is safe. For time-sensitive approvals, also check the vendor's advisories.

What to do with a warning

An advisory is information, not an automatic decision — octoja never withholds an update on its own. You have three ways to react, all reachable from the same page:

Let a policy act on advisories for you

Reviewing every KB by hand does not scale across a fleet. A patch policy can therefore take known issues into account on its own: enable the option to exclude updates with known problems in the policy, and updates that carry an advisory are held back from that policy's cycles without you touching them. Combine it with a maturity delay of a few days in your approval rules and the common case takes care of itself — you only look at the catalog when you want to overrule something.

Policy setup is described in Set up patch policies and cycles; blocking and exclusions are covered in Exclude or block updates.

Tips

• Read the badge before the text. A Confirmed entry is an acknowledged problem; a community report is a pattern, which can also mean a handful of partners were unusually cautious.
• Follow the link when a warning would change your plan. The panels summarise; the linked advisory tells you which builds and configurations are actually affected.
• Ignoring a KB is not just a local decision — it feeds the community signal that warns the next partner. Setting an update to ignored when it genuinely caused you trouble helps everyone.
• A blocked update stays blocked until you lift the block, including in emergency cycles. Note somewhere why you blocked it, so it does not quietly stay out of your fleet for months.