It might help if you the microflow itself so we can see what is happening
What is the https://docs.mendix.com/refguide/mx-assist-performance-bot/ telling you?
I assume that ACT_get_list is used as a SUB_get_list called from the main Microflow. If not (so triggered by a button) we are observing user waiting time in the log.
It looks like the Server is waiting for resources to call the ACT_get_list or the network is the problem. Have you looked at it from the developers tools → network viewpoint?
(In Chrome <Ctrl>+<Shift>+<I> → Network tab?
Can you share that view:
Go Make It
Hi Shriram Patil,
While retrieving from database you can always use indexing feature in the entity. Indexes improve the speed of retrieving objects if the indexed attributes are used in a search field, the XPath constraint of a data grid or template grid, or a WHERE clause of an OQL query. However, search fields where the
Comparison property has value
Contains do not take advantage of the improved performance.
Hope it helps. Let me know if you face issues around it or if you were looking for something else.