Projects stuck in Recovering acceptance after a draft merge
We have deployed the fix and resolved the issue that caused projects to get stuck on "Recovering acceptance" after merging a draft. If your project is still stuck, please retry to allow it to recover and resume editing and building.
The latest update from Lovable.
State
Resolved
Started
Lasted
1 h 27 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
56 min 64%
Identified
31 min 36%
Updates
Times in UTCAs posted by Lovable
We have deployed the fix and resolved the issue that caused projects to get stuck on "Recovering acceptance" after merging a draft. If your project is still stuck, please retry to allow it to recover and resume editing and building.
Affected projects remain stuck on "Recovering acceptance" after merging a draft, preventing editing and building. We have identified the issue and prepared a fix. We expect deployment to complete in approximately 35 minutes. Once the fix is fully deployed, retrying should allow affected projects to recover. Projects not using drafts remain unaffected.
Projects affected by the draft merge issue are unable to edit, in addition to being stuck on "Recovering acceptance". We are investigating the issue and working to restore editing and building for affected projects. Projects not using drafts are unaffected.
Some projects are getting stuck on "Recovering acceptance" after merging a draft, preventing the merge from completing. We are investigating the issue.
Lovable in the last 90 days
Full historyIncidents in 90 days
25
Days with an incident
19
Median duration
57 min
This incident
1.5× the median
Other Lovable incidents
All incidentsLovable·Some Lovable Cloud apps unable to reach backend
This incident has been resolved.
Lovable·Chat and project changes are currently failing for some users
This incident has been resolved
Lovable·Some users may see errors when setting up a database or backend for a new project, or when remixing a project.
Some users may see errors when setting up a database or backend for a new project, or when remixing a project. Our team is investigating.
Lovable·Enabling Lovable Cloud on projects is currently failing for some users
This incident has been resolved.
Lovable·Lovable is slow at answering
Service is returning to normal. Any delayed messages should be handled within 10-20 minutes at most.
Follow Lovable
Your coding agent knows when Lovable is down, and tells you when a failure is theirs, not yours. You can also get Lovable incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "lovable" and tell me if Lovable has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=lovable/feed subscribe https://outages.live/feed.xml?providers=lovableFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane