This is a problem we've run into a 3rd time, eventually the amount of metadata accumulated in the postgres database causes the API to exceed AWS' 10MB limit for the api gateway. In the past we've punted, abandoned the postgres db and re-run the CF stack to get a new metaflow instance. Is there a more elegant solution? We've added many filters to our flow retrieval, but this doesn't seem to help. Any suggestions would be greatly appreciated.

Which API endpoint are you referring to?

this is when making a post request to the metadata service from a metaflow flow? how is the error manifesting?

@square-wire-39606 my analysis was wrong. It is NOT the 10MB Api gateway limit. The problem is somewhere within the metadata-service-v2.