Trying to make sense of why the custom data action hits rate limits immediately. Running JMeter with 50 threads from Singapore against the integration endpoint. Getting 429 errors after just 10 concurrent calls despite low overall volume. Payload below:
The root cause here is the default rate limit on custom integration endpoints, which is strict regardless of geographic origin. The 429s indicate you hit the threshold for that specific action type. Try adding a retry-after header check in your JMeter script or implement exponential backoff. Alternatively, verify if the integration uses a dedicated tenant with higher limits, as shared tenants have stricter caps. Check the X-RateLimit-Remaining header in response.