Hello
I’ve been running a high-frequency transaction script on Polygon & I’m facing intermittent failures due to RPC rate limits. Sometimes; transactions fail to broadcast or get stuck in a pending state for an unusually long time, even when gas fees are appropriate. 
Other times; I receive 429 Too Many Requests errors, despite spacing out requests within the advertised limits.
This issue is especially problematic when interacting with smart contracts requiring multiple sequential calls; as one failed request can disrupt the entire process.
I’ve tested multiple RPC providers; including public and private nodes, but the issue persists, particularly during high network congestion. 
I suspect that Polygon’s public RPCs may have hidden rate limits beyond what’s officially documented. Another concern is whether fallback RPCs can be configured dynamically to avoid disruptions when one provider enforces stricter limits. Checked https://docs.polygon.technology/pos/reference/rpc-endpoints/selenium training online guide related to this and found it quite informative.
Has anyone else encountered unreliable transaction handling due to RPC rate limits? 
Are there any best practices for managing high-frequency interactions with Polygon’s network? I’d appreciate insights from other developers on how to ensure smooth transaction execution.
Thank you!! 