Non-persistent objects not cleared from memory when API microflow completes, causing thread count to reach maximum level

It seems that our microflows that are handling API requests coming into the Mendix application are creating non-persistent objects, which are staying in memory as a session is maintained for our “apirestuser” in between API requests. This is the cause of a growing thread count problem and we are wondering what action we can take to ensure that the API requests are releasing their objects in memory after they complete? Do we need to convert all these non-persistent objects to be persistent, even though that’s not what we want? Is there a way to signify that a session should not be maintained for that request?
0 answers