While I know there are updates being hammered on right now which reduce the API workload, I still think the plugin should be more resilient to network and rate-limiting failures and attempt some form of retry.

See the attached screenshot, if one is particularly unlucky (which I seem to be), a number of pull requests will be "stuck" in this "Some checks haven't completed yet" indefinitely.

When I click through on "Details" however, the entirely Pipeline run had passed ages ago, and at the end of the Console Output lies: Could not update commit status. Message: GitHub API rate limit exceeded

Perhaps a built-in queue of commit status updates could be utilized, and when the rate-limit is lifted, Jenkins could re-send the commit status updates?

Something, anything, would be better than the suspenseful yellow ball in GitHub