Issue Summary

When running the api call /rest/api/2/user/picker?query=<username> (or /rest/api/3/user/search) continuously, the api call at times will  give a response with 200 OK but zero results. In the back-end, we see it is actually hitting 429 (rate limiting). Need to propagate 429 as a response for the api call too.

Steps to Reproduce

1. Run /rest/api/2/user/picker?query=<username> (or /rest/api/3/user/search) multiple times.
2. Most of the times it gives a result.
3. At times it will give an empty list with 200 OK response – On checking the back-end we see it actually hitting the rate limiting with a 429 error code.

Expected Results

It should give a 429, as seen in the backend. This way the customers can understand that they are actually hitting the rate limit.

Actual Results

The below errors are found in the logs:

{"users":[],"total":0,"header":"Showing 0 of 0 matching users"}

CPUS returned unexpected status code: 429 for tenants XXXXXXXXXXXXX and principal XXXXXXXXXX

Workaround

No workaround.

This is more of a missing information that the customer's are not receiving and creating confusion.