Slack integration - Hitting Slack rate limit when using API's to create alerts gives wrong error message

### Environment SaaS ([https://sentry.io/](<https://sentry.io/>)) ### Steps to Reproduce 1. Create/edit multiple alerts through [https://sentry.io/api/0/organizations//alert-rules//](<https://sentry.io/api/0/organizations//alert-rules//>) 2. make sure you set a slack action step to a channel ### Expected Result When Slack is rate limiting the requests it should be clear within Sentry users why it has been failing. ### Actual Result Error message is: (ERROR): failed to update transactionsVolume, 400 given. Received: {"nonFieldErrors":\["Could not retrieve Slack channel information."\]} While internally we get "The Slack API responded with {'ok': False, 'error': 'ratelimited'}" We likely will need to add a rate limit check [here](<https://github.com/getsentry/sentry/blob/b139a0ca17a12a3f8f5c7b43fa8c4ddc85a45f1c/src/sentry/integrations/slack/utils/channel.py#L122-L125>). ### Product Area Settings - Integrations ### Link *No response* ### DSN *No response* ### Version *No response* ┆Issue is synchronized with this [Jira Improvement](<https://getsentry.atlassian.net/browse/FEEDBACK-2342>) by [Unito](<https://www.unito.io>) We want to define a set of [lightweight metrics](<https://docs.sentry.io/product/explore/metrics/>) that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that **do NOT overlap with Tracing**. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.<br><br>Examples**:** * Node.js runtime metrics (e.g., event loop delay, heap usage) * Prisma-related metrics in Next.js * Mobile CPU / memory usage to help surface potential ANRs or app hangs --- **Candidate Metrics (add more below)** * … *(please also add ideas, questions or examples in comments)*