Volume snapshot stuck as “already scheduled” since Nov 2 — scheduled snapshots also stopped

Questions / Help
1

Hi, volume vol_r1jdowonl9kqep0r (region gru) cannot be snapshotted since Nov 2, 2026. Every fly volumes snapshots create returns:
failed_precondition: snapshot is already scheduled at 2026-11-02T12:40:51Z
That snapshot never appears in fly volumes snapshots list, and the daily scheduled snapshots stopped too (the last ones are from Nov 1). I already toggled --scheduled-snapshots=false and back to true; the error persists. Other volumes in the same org snapshot fine. Could you clear the stuck snapshot job? Latest request ID: 01M6GYNNVBV1VZEWFG5KVPE1H-gru.
Thanks!

2

Same issue as Cannot create volume snapshots only in GRU (May 2025, also GRU) — snapshot request never completes and blocks new ones.

3

Hi! We stopped the stuck snapshot request and started a new one in its place. A fresh snapshot has now been created, and automatic backups for this volume should resume as scheduled (hat-tip to @TomR who fixed this).

Let us know if anything still looks off!

4

Thanks, confirmed working: the new snapshots are there and a manual snapshot now completes fine.