@burstrom this is because the revert failed. This is a known issue and should be fixed with a memory improvement in Vapor Cloud. Basically the current free container is too close to the memory limit, so when you run the revert it takes up too much memory and fails. A change in the Vapor Cloud container is coming which reduces the memory footprint. If you try deploying again and then reverting again in a couple of days this issue should be fixed.
The workaround for now is to delete the database from the dashboard in Vapor Cloud and create a new one when you deploy.