If a user uses the Shift+Click feature to bulk-select proposals/candidates, they can easily exceed the API rate limit because each proposal/candidate is updated with a separate request.
To fix this, update the proposal/candidate API endpoints to accept a list of up to 100 updated proposals/candidates (similar to the annotation bulk API endpoint). In the frontend, the single change then sends a request with a single list item. A bulk-select action, however, now sends bulk requests, too (splitting the actual number of changed proposals/candidates into chunks of 100).
If a user uses the Shift+Click feature to bulk-select proposals/candidates, they can easily exceed the API rate limit because each proposal/candidate is updated with a separate request.
To fix this, update the proposal/candidate API endpoints to accept a list of up to 100 updated proposals/candidates (similar to the annotation bulk API endpoint). In the frontend, the single change then sends a request with a single list item. A bulk-select action, however, now sends bulk requests, too (splitting the actual number of changed proposals/candidates into chunks of 100).