Question 1
AdvancedDesign Your Workflows: Spotlight on Slack's APIs · Process rate limits throughout the Slack platform
A financial services firm is developing a custom Slack app to assist traders with real-time stock analysis. The app currently uses the Web API to post market updates every 10 seconds to a high-traffic channel. During peak trading hours, the app frequently receives HTTP 429 Too Many Requests errors. The architectural team needs to redesign the communication flow to respect Slack's rate limits while ensuring traders receive timely updates. Which approach offers the MOST scalable solution?
Answer and explanation
Correct answer: A
The optimal solution for high-frequency updates that hit rate limits is to consolidate information. By using chat.update to refresh a single 'dashboard' message or consolidating multiple updates into a batched message, the app reduces API calls. Crucially, any robust app must implement a queue that pauses requests based on the Retry-After header provided by Slack in 429 responses.
