mgetrequests refer to request's that come from a lookup of a unique ID stored on another object. For example, if a User has a list of Stores (another object in your DB) stored directly on the User object, it is really storing a list of Stores' unique IDs. When you want to display some data about those Stores, or filter them or do some operation with them, an
mgetrequest is sent.
Current User's Stores's Namewould request all the Stores in this List of Stores.
searchrequest on your page that seems to be causing issues (downloading lots of data or holding up page loads), it's sometimes difficult to identify what is actually causing that search to be downloaded onto the page, since they aren't usually caused by simple searches. Maybe a condition on an element that causes the element to be visible - maybe a :sort when referring to a Repeating Group's content.
mgetrequest that is inefficient, you may have trouble finding the source of that request if you're on a page with many searches.
msearchrequests, but we've had less luck with them.
search_pathcode, you need to paste it into the Console tab of the Chrome DevTools. The Chrome DevTools should be opened from your Bubble Editor for that app, not from the preview mode of the app (i.e. NOT from the same DevTools window where you found the
Repeating Group's Users:filteredas a data source.