Stop deferring PublishCommentsWorker on database health

What does this MR do and why?

PublishCommentsWorker posts the findings of a Duo Code Review to the merge request. It deferred on the gitlab_main health signal, which is meant for low urgency background work. While the signal stays at stop, the deferral delay grows up to 30 minutes for each retry, so the job can wait longer than the 1 hour review timeout. TimeoutWorker then posts "Something went wrong" and deletes the progress note, and the late job posts nothing.

The worker is high urgency, a user waits for it, and it only writes a few notes, so it no longer defers.

References

Screenshots or screen recordings

Before After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports

Loading
Loading