yeah we’re fixing that. It’s a small configuration issue with the database where its holding onto old reader transactions and keeping multiple copies of the database. We had to push out the storage debugger/ui to find the issue so its been a process