Comment 11 for bug 311690

This is almost certainly fallout from database replication. During normal operation, it will take 30-60 seconds for the information about the upload to propagate to the replica database. It is quite likely that when attempting to view this page with a web browser, the replica database is hit and the information doesn't yet exist.

It may be a simple solution to force the use of the master for this particular page. This would be a malone fix.

An alternative is to update the publisher so, if a 404 is generated and the replica database used, the request is retried using the master database (quite similar to the Retry mechanism used to handle database deadlocks and serialization exceptions). This would be an infrastructure fix.