Certification failed
A certification campaign failed to generate or complete.
Certification generation failures usually come from the population/scope definition, missing owners, or performance limits on large campaigns.
- Symptom: A certification campaign failed to generate or complete.
- Most likely causes
- Step-by-step fixes
- How to prevent recurrence
A certification campaign failed to generate, or did not complete as expected. Because certifications are the primary compliance-evidence mechanism, a failed campaign is both an operational and an audit problem.
Start here: read the evidence
Open the certification generation task result. Campaign generation is a task like any other, and its result names the cause, usually scope, ownership or scale.
Likely causes, in order
- Bad population or scope definition, the campaign targets nothing, or far too much.
- Missing certifier/owner, items have no one to review them.
- Very large campaign hitting performance or memory limits during generation.
- Rule error in a certification exclusion or assignment rule.
How to fix it
- Read the generation task result for the specific error.
- Verify the campaign population and that certifiers/owners are assigned.
- Split very large campaigns into smaller, phased campaigns.
- Fix owner assignments and any certification rules.
- Regenerate and monitor to completion.
Preventing recurrence
Enrich entitlements with owners so certifiers always exist, scope campaigns to reviewable sizes, and prefer targeted, event-based certifications over enormous annual sweeps that strain generation.
Common pitfalls
- Guessing instead of reading the task/transaction result, which usually names the cause.
- Fixing the symptom, not the root cause, so it returns.
- Changing several things at once, so you cannot tell what worked.