At 7:15 a.m. on October 24th, Hong Kong time, the API returned a token rate limit error, but no token rate limit was found on the monitor.
- Monitoring found call anomalies, but no token rate limit was found.
- The token rate limit set by the service is 240k, but the monitoring shows that it has not been reached.
- I would like to know the token rate limit request statistics. Is it based on the number of visits or the number of completed processes?
- Monitor the ratelimit information. Why can’t I see an exceeded curve?