In your workspace, you are able to define settings for whether or not your request history data is stored. When you select "Enable" you are met with an additional dropdown that asks how many statements should be stored so in this article we will dive a little deeper into that.
Firstly, the limits are related strictly to your function stack and are not a setting to limit how many request history items that specific object type will store. In other words, if you API gets called 2000 times, 2000 request history items will be stored.
What the limit does, is control how many of your function stack items are displayed. For example, in this API, I have set the limits to store no statements:
and the result is as follows:
When I set the API to limit it to only x amount of statements, the result is as follows:
"So what is the point?"
This feature is mainly useful for object types that might have loops that run through a large amount of data and in the end, generate a lot of statements due to the repetition of statements being triggered from the loop.
For troubleshooting purposes, you may be curious to know at which point the function stack stopped running and having a view of all the statements might give you that context. However, if you only want to know what the inputs, outputs and duration of the call were, you might not need to store the statements at all.
The use of this feature is conditional to what you are looking to know about each call made to any of your object types.