← Back to Fly.io History
minor✓ Resolved

flyctl deploy creating new app instances

Fly.ioTue, Apr 28, 2026, 11:50 PM
Status
resolved
Duration
54 minutes
Updates
3
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedWed, Apr 29, 2026, 12:45 AM
This incident has been resolved.
monitoringWed, Apr 29, 2026, 12:31 AM
A fix has been implemented and we are monitoring the results.
identifiedWed, Apr 29, 2026, 12:07 AM
The issue has been identified and a fix is being implemented.
investigatingTue, Apr 28, 2026, 11:50 PM
We're investigating an issue where fly deploy is creating new Fly machine instances rather than updating existing ones, leading to apps with a mixed state. We're currently investigating the issue. As a workaround, please try removing the "processes = [ "app" ]" line from your fly.toml configuration file and redeploying. Another workaround is to downgrade flyctl to 0.4.40 - this should resolve the issue in the meantime.

📊 TECHNICAL DETAILS

Internal ID
b087d1ad-9c04-45ee-b18f-3c4b68efc896
External ID
6kyrwz51cv9n
🕐 Started
Tue, Apr 28, 2026, 11:50 PM
🔄 Last Updated
Wed, Apr 29, 2026, 12:45 AM
✓ Resolved
Wed, Apr 29, 2026, 12:45 AM
MINOR
Impact Level
54 minutes
Total Duration
3
Status Updates
Affected Components
Deployments
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed