<![CDATA[Persistent AB1021 rate-limit error on getCandleData despite low request rate]]>Update: This is not a one-day issue. On a completely fresh day (2026-08-11),
restarting the bot from scratch, I got AB1021 "Too many requests" on the very
first candle scan (09:20:02), before even completing 12 sequential requests
spaced 6+ seconds apart. This confirms it's a persistent account-level
restriction, not a temporary burst-triggered cooldown.

]]>https://smartapi.angelone.in/smartapi/forum/topic/5637/persistent-ab1021-rate-limit-error-on-getcandledata-despite-low-request-rateRSS for NodeMon, 17 Aug 2026 03:59:58 GMTTue, 11 Aug 2026 03:56:49 GMT60<![CDATA[Reply to Persistent AB1021 rate-limit error on getCandleData despite low request rate on Thu, 13 Aug 2026 05:50:33 GMT]]>Same issue here — running a Nifty-options intraday bot polling getCandleData (FIVE_MINUTE) once every 5 minutes, ~0.003 req/s against the documented 3 req/s/client cap. Comparing the identical 09:15-10:35 window across three consecutive sessions: 12, then 17, then 27 rate-limit rejections, and the last two days both fully exhausted a 6-attempt retry budget on the very first request of the day, before any other call had been made.

That makes six independent reports of this exact symptom now, across two different endpoints — candle data and order book — all well under documented limits: 5636/5637, 5611, 5625, 5595, 5560. I've put together a fuller writeup with the full data here: https://smartapi.angelbroking.com/smartapi/forum/topic/5639/getcandledata-rate-limit-false-positives-at-0-003-req-sec-six-independent-reports-zero-acknowledgment

Would genuinely appreciate an actual look at the server-side telemetry rather than another "can't help with your code" response.

]]>https://smartapi.angelone.in/smartapi/forum/post/19222https://smartapi.angelone.in/smartapi/forum/post/19222Thu, 13 Aug 2026 05:50:33 GMT