updateLegalTagStatus API throwing `509` errors

We are observing frequent 509 response from the API when an environment have lot of data-partitions (over 25).

GET /api/legal/v1/jobs/updateLegalTagStatus API updates LegalTag status based on expiration and typically invoked by CRON on a schedule. Currently this API iterates over all partitions and required to be only invoked once for an environment. When we get response with 509 error code, API doesn't finish processing all data-partitions and even leave LegalTags on a data-partition in inconsistent state.

In M23, we have further extended this API to add new feature: catch about to expire legal tags. This again adds on to the issue and degrades the performance further.