Machines REST API returns HTTP 412 when attaching a restored, unattached volume in iad

I’m trying to recover a persistent SQLite checkpoint from a restored Fly volume.

A Machines REST API POST to create a stopped Machine using that volume returned HTTP 412.

Read-only checks afterward confirmed:

  • The recovery app has zero Machines.

  • The restored volume is in created state.

  • The volume is unattached.

  • Region: iad.

  • Host status: ok.

  • No successful Machine creation occurred.

The saved response did not retain the explanatory error body or request correlation ID.

Could Fly staff help identify which precondition could cause HTTP 412 in this situation?

I’m particularly interested in whether a stale volume claim, deleted-Machine association, or host-placement restriction might explain the rejection.

I can provide the app name, volume ID, and approximate UTC request window privately if needed.

Please treat this as investigation only. I don’t want any existing volumes or Machines modified or deleted.

please read the response body, it will give you the information you are looking for.

off the top of my head, the most likely case is the host your Volume is on does not have enough capacity available for the Machine you are trying to create (our docs talk a little about this). if that’s the case (double-check the response body), you can fork the volume (in Machines API this is creating a new volume with source_volume_id key), I recommend using compute object so the new Volume is created on a host with enough capacity for your Machine.