Deployment Fails Due to Billing Issues After Using Linked Organization

Hello,

I am facing a deployment issue on Fly.io after merging two organizations under one billing account.

When deploying for the drop-79 organization, I get the following error:

Updating existing machines in 'andasy-docs' with rolling strategy  
Failed to update machines: failed to update machine 1852011a343d28: failed to update VM 1852011a343d28: We require your billing information, please add it at https://fly.io/dashboard/drop-79/billing  
Retrying...

Here is the background:

  • We merged two organizations, drop-79 and quarksgroup, under a single billing structure.
  • The billing for both organizations is managed by quarksgroup, and all invoices are being paid successfully.
  • Deployments for the quarksgroup organization work without any issues.
  • However, deployments for the drop-79 organization fail with the above error, seemingly because it is still checking for billing information in drop-79 directly.

I suspect there might be a misconfiguration in how the merged billing setup is being recognized by Fly.io.

Could someone assist with resolving this issue?

Thank you!

Hi there,

Please shoot us an email at billing@fly.io and we’ll get you sorted out!

  • Daniel

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