Stacktorm UI can't go further than page 3

SUMMARY

Stackstorm web UI can't go further than page4

STACKSTORM VERSION

st2 3.7.0 st2web 3.7.0 mongodb 4.0.0

OS, environment, install method

RHEL7, upgrade to 3.7.0 from 3.4.1 by RPM

Steps to reproduce the problem

Show how to reproduce the problem, using a minimal test-case. Make sure to include any content
(pack content - workflows, actions, etc.) which are needed to reproduce the problem.

Expected Results

1 navigate to UI https://xx.xx.xx.xx/#/history

2, click "OLDER" button to go to next page

3, after navigate to page4, it pops up error box in left-bottom of page

4, check with st2api.log, found error like below:

pymongo.errors.OperationFailure: Executor error during find command :: caused by :: Sort operation used more than the maximum 335544320 bytes of RAM. Add an index, or specify a smaller limit., full error: {'ok': 0.0, 'errmsg': 'Executor error during find command :: caused by :: Sort operation used more than the maximum 335544320 bytes of RAM. Add an index, or specify a smaller limit.', 'code': 96, 'codeName': 'OperationFailed'}

5, reset mongodb attribute by command to expand query blocking bit to 503316480 (based on error message to google)
db.adminCommand({setParameter: 1, internalQueryExecMaxBlockingSortBytes: 503316480})

6, back to Web UI, the page 4 display

7, continue to click "OLDER" button

8, the same error show again when it goes to page 7.

Actual Results

The web UI should show every page properly. How to fixed it except setting internalQueryExecMaxBlockingSortBytes to larger vaule in mongodb

Thanks!

Start with the history UI route at #/history and the st2api.log entry showing MongoDB's blocking sort memory error; reproduce it by repeatedly clicking "OLDER". Trace the history-page query and its pagination and sorting behavior, then verify that later pages load without requiring a larger MongoDB sort-memory setting.