When the coverage report is generated, it only fails a job for a given code state once if the coverage values are outside of the configured levels and `Mark Unhealthy as failed` is checked.

For example, a coverage of git sha abcdef with Package Coverage set to Unhealthy below 80% and actual coverage at 73% will fail once.

If the job is run again targeting the same git sha (abcdef) without changing the Coverage acceptance levels, the job will succeed even though Package Coverage is still at 73% and should be marked as Unhealthy (and fail).