Issue
An external service publishes successfully during light testing but receives throttles at production traffic.
Cause
The project treats Open Cloud and engine calls as unrelated unlimited channels or publishes one message per tiny event.
Fix
Follow the unified current rate-limit model, batch appropriate notifications, deduplicate repeated state, and retry with bounded backoff. Use MessagingService for transient coordination, not durable storage or guaranteed delivery.
Verify
Load-test below and above expected peak, record throttle responses, and confirm consumers tolerate duplicates and missed messages.
Official Roblox MessagingService update recap
#1
Original Heliotrope guidance with authoritative Roblox sources.