docs: clarify legacy blocker resolution limits
This commit is contained in:
@@ -90,6 +90,11 @@ with pagination; event rows expose related job/product links when present.
|
||||
Blocker details show evidence, first/last seen, retry count, related
|
||||
events/jobs, and resolution audit history when available.
|
||||
|
||||
Legacy blocker rows without a persisted installation binding remain visible at
|
||||
tenant level, but the panel does not offer context resolution or reprocessing
|
||||
for them. The detail page explains that an exact server cannot be proven; direct
|
||||
resolution attempts return a conflict rather than guessing an Agent.
|
||||
|
||||
Resolving a blocker means saving validated operator context and queueing
|
||||
reprocessing for that product; it does not directly write fiscal data or
|
||||
immediately mark historical blocker evidence resolved. The workflow requires a
|
||||
|
||||
Reference in New Issue
Block a user