Cannot create volume snapshots only in GRU

Creating snapshots in GRU is not working right now (and I think it hasn’t been working since May 14th, 2025):

fly volumes create my-volume --region gru

Then figuring out the volume id that was created and trying to run:

fly volumes snapshots create {volume_id}

Requests a snapshot that never finishes and that prevents us from being able to request it again (because the same CLI command returns an error saying that there is a snapshot that was already requested).

Error: failed to snapshot vol_xxxxx: failed_precondition: snapshot is already scheduled at 2025-05-27T19:17:49Z (Request ID: 01JW9M6FMJS3QF5TFX7BND59WG-gru)

I have confirmed that this issue does not happen in IAD or GIG however I’m unable to use the snapshot functionality that Fly provides right now.

Has anyone seen this before? I even tried with different accounts/orgs and still got the same results.

2 Likes

I was hoping this bug would be fix here

But the problem persists.

This error below is shown when trying to fork our database:

Error: timeout reached waiting for machine's state to change
The machine {machine_id} took more than 5m0s to reach "started"

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.