[Providers][Slack] Add automatic 429‑retry to channel‑lookup logic #51265
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #47225
🐞 Problem
SlackAPIFileOperatorlooks up channel names withconversations.list(a Tier‑2 Slack API,≈ 20 req/min). When a DAG fires many parallel tasks, these look‑ups quickly hit
HTTP 429 rate_limited errors and the tasks fail.
Reference: https://api.slack.com/apis/rate-limits
How to reproduce
Running the DAG returns multiple SlackApiError: ratelimited exceptions.

Screenshot (before fix):
✅ Fix
SlackHook._call_conversations_list()now retries up to 5 times when Slack respondswith 429, respecting the
Retry‑Afterheader.AirflowException("Max retries reached for conversations.list").This keeps the operator working without changing user DAGs.
Verified in a local Breeze environment against a test Slack workspace:

Unit tests added