Describe the bug
Following the ticket: #5851

We're still experiencing this issues even in the newer redis search version (2.10.17).

Currently, we've upgraded our Azure resource configuration as follows:
Balanced: 32 vCPUs, 120 GB cache, SKU B100
Redis Search module version: 2.10.17

Unfortunately, the issue persists.
Our use case involves querying and retrieving approximately 80,000 documents daily. However, we often have to retry the operation several times to retrieve the full dataset, as we occasionally receive empty array results toward the end of the process, as mentioned previously.

This issue is also occasionally reproduced even when we're not using CURSOR or SORTBY.

Is there any alternative solution or recommended workaround for this behavior?

To Reproduce
Steps to reproduce the behavior:
Query: FT.AGGREGATE asset_idx "(@HierL1:{7} @HierL2:{2} @HierL3:{22})" TIMEOUT 15000 LOAD 13 @Id @LastReadTS @Name @LastReadPct @LevelStatusEnum @D_SerialNo @LastReadVol @CapMeasUnit @A_Id @AvgDailyCons @IntProdType @T_DistributorId @T_DistributorName

Expected behavior
Receive all documents (without getting "empty arrays")

Screenshots

Environment (please complete the following information):

• Azure Managed Redis Balanced: 32 vCPUs, 120 GB cache, SKU B100
• Redis Search module version: 2.10.17

Additional context
Previous ticket