Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notifications are failing because of Slack Rate Limit with no Workaround. #426

Closed
scott-hill-alkami opened this issue Sep 29, 2023 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@scott-hill-alkami
Copy link

Orb version:

slack: circleci/slack@4.5.0

What happened:

CircleCI jobs are failing the Slack - Sending Notification step

CircleCI build: https://app.circleci.com/pipelines/github/Alkami/configuration-utility/14481/workflows/3b13f8db-c6e2-4ff6-841c-5f77e14e72ff/jobs/14291

Slack - Sending Notification
Posting Status
Checking For JQ + CURL: Debian
Sending to Slack Channel: mobile-status
Exited with code exit status 22

I'm seeing this message in our Slack channel as well:
Due to a high volume of activity, we are not displaying some messages sent by this application. • Details

Expected behavior:

Successfully send the message, maybe retry after a second or two?

Additional Information:

There is currently no workaround or this failure. Once the Rate Limit is hit all notifications fail.
We need a retry loop here with a parameter to set the number of retries... maybe default to 0
An onion to set the seconds-to-wait-between-retries as well would be nice.

@scott-hill-alkami scott-hill-alkami added the bug Something isn't working label Sep 29, 2023
@marboledacci marboledacci self-assigned this Oct 22, 2024
@marboledacci
Copy link
Contributor

There is a retry option now in version 5.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants