In order to better control the process data cleanup which is batched from the side of Optimize now, the batch size should be configurable for cases where the request size of delete by id queries might exceed request limit sizes (thinking e.g. of aws elasticsearch deployments). Usually customers shouldn't need to adjust this, it's intended of a last resort in such cases.
- history cleanup batch size is configurable
Docs will be amended with