Here’s a quick update: our volumes list endpoint was running slow for folks with several volumes on the same app so we did some tweaks and this endpoint should be way faster on these cases now!
Also we will not be displaying volumes in
destroying state there, we used to hide those on our GraphQL endpoints so we just making sure that folks coming to machines API have the same experience.
In case you’re curious here’s what
- Your volume is scheduled to be destroyed for real
- You’re not being billed at all during this state
- There’s no way to bring it back unless you use snapshots (assuming they’re still available). Destroying volumes is a dangerous operation so be careful.