Live

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 updates
22:1922:4123:0323:2523:46
DegradedUpdate postedTimes in UTC

Investigating

56 min 64%

Identified

31 min 36%

Updates

Times in UTC

As posted by Lovable

Resolved

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.

Identified

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.

Investigating

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.

Investigating

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 history
90 days agoToday

Incidents in 90 days

25

Days with an incident

19

Median duration

57 min

This incident

1.5× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 h 51 min
median 57 min
90 days agoToday

Other Lovable incidents

All incidents

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=lovable
Slack
/feed subscribe https://outages.live/feed.xml?providers=lovable

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane