Matthew Elwell

> Wouldnt tags be better for this? Yes, perhaps.

At the moment, the responses to flags (from the Core API) includes the feature `description` and `tags` fields. These are not necessary to return and potentially sensitive.

I am not able to reproduce this in production.  @dabeeeenster can you provide a project / environment / feature where you are able to consistently reproduce please?

To update here, I was able to reproduce this only in our Flagsmith Website project but I am able to consistently reproduce it for all feature / segment combinations in...

After enabling the sentry tracing stuff discussed above, this trace should give us the information we're looking for: https://sentry.io/organizations/flagsmith/performance/flagsmith-api:897e88964e5c4[…]Fv1%2Ffeatures%2Ffeature-segments%2F&unselectedSeries=p100%28%29 There are an awful lot of queries happening in that trace...

Interestingly, just creating a feature looks like it has the same issue. There's something happening after a request to create an entity in our database which is spawning ~200 additional...

Ok, it seems like the probable cause of this is the data transfer to dynamo db. A quick test turning off 'enable dynamo db' for one of my projects reduces...

This has been moved to a hook on the AuditLog object in Gagan's PR #2179 and AuditLog records are written asynchronously so maybe this is complete as part of that.

Nope.

This is done in core. The edge requirement is going to be solved by limiting the number of identity overrides as per #1675