Revisions and Commits
In the end, it's not necessarily data  which is obsolete. It's more having
partial production dump mounted on staging. We have dangling data.
For example, recently a dumps with origin/origin-visits was mounted. This means
we reference snapshot which do not exist right now.
That's making the npm/pypi/etc... loaders blow up. I'm fixing that in the
loader for now. It's a technical path which could happen in production anyway
(because the storage api used in the loader allows it)...
 I was referring to scheduling data