The setupdb app has a mode where it'll generate fake data. The way it works is by generating a bunch of random processed crash data for a non-existent product and then putting that in postgres. There's another script for syncing that data with Elasticsearch. Pretty sure this ignore S3.
Thus, fake data generation results in a state that's missing bits and who knows how that works in the webapp.
I think this code isn't really helpful anymore especially in light of improvements to the local dev environment.
This bug covers removing the setupdb app fake data generation code and the helper script for syncing it to Elasticsearch.