[wp-trac] [WordPress Trac] #61701: Rate limiting can occur when sending Slack notifications out through GitHub Actions

[WordPress Trac]

#61701: Rate limiting can occur when sending Slack notifications out through GitHub
Actions
------------------------------+--------------------
 Reporter:  desrosj           |      Owner:  (none)
     Type:  defect (bug)      |     Status:  new
 Priority:  normal            |  Milestone:  6.7
Component:  Build/Test Tools  |    Version:
 Severity:  normal            |   Keywords:
  Focuses:                    |
------------------------------+--------------------
 In some scenarios, Slack notifications being sent through GitHub Actions
 are being rate limited. This is mainly happening when the scheduled
 testing of old branches able to receive security updates kicks off, but it
 could happen any time there is enough of a volume of events that send
 notifications.

 This seems to happen because of how GHA jobs are queued and picked up.
 Since the Slack notification step is a separate job, many are queued while
 waiting for the completion of more time intensive ones, such as PHPUnit or
 E2E testing. While Slack does not publish exact parameters for rate
 limiting, they are [https://api.slack.com/apis/rate-limits#overview
 documented for webhooks as 1 per second with short bursts >1 allowed].

 There's currently [https://github.com/slackapi/slack-github-
 action/issues/245 no built in way for the Slack action to handle this],
 though [https://github.com/slackapi/slack-github-action/issues/312 retries
 for failed calls is being discussed as a possible feature for V2] of the
 action.

 It would be great to find a way to retry or space out these attempts until
 then to prevent workflow failures from occurring solely because the
 notification is unsuccessful.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/61701>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform