History not available if too many deployments

[exalate-issue-sync]

Describe the bug :

When we have an API that is complex, meaning it has many, many flows and policies on each flow, and we deploy it a couple of hundred times, when we want to display the history we will get either unable to reach server as the request times out or the UI will glitch out and everything concerning this API will then be slow and unstable. We tried using a complex API and we ran a script which changed something to the API each run and deployed it and before reaching 500 runs the Management API crashed and the API was unstable. Now the workaround that is discussed is to limit the last 100 deployments to be viewed for an API.

To Reproduce :

Steps to reproduce the behaviour:

1. Create an API with many flows and policies on each fow
2. Make sure to publish the API a couple of hundred times (ex. 500 times)
3. If the Management API is stable, try to access history of the API
4. You either will get a server unreachable or a very unstable and slow API

Expected behaviour :

To display history without issues

Desktop :

• Environment: [3.20.16]
• Browser [Chrome]

[exalate-issue-sync]

This issue will be fixed in versions 4.0.13, 3.20.24, 4.2.0, 4.1.4