
Fix is out for older bots stuck after the account merge
Bots you had before merging into The X Subscription should reply again. Messages sent while they were stuck won't run, so send a new one.
If your older bots went quiet after you merged your Cursor account into The X Subscription, send each one a new message now. Cursor staff Colin said at 8:34 AM ET that "The fix has now gone out to every affected account," so "the bots you had before the merge should reply again."
- Status: Fixed for every affected account, per staff.
- Catch: "Messages sent while they were stuck won’t be picked up on their own."
- What to do: Send a fresh message to each older bot, then check its routines.
What changed#
On Oct 13 at 6:04 PM ET Colin explained that the merge "didn’t finish re-linking" pre-merge bots to the merged sign-in, so messages were accepted but never started, and "Scheduled routines on those older bots are affected the same way." Bots made after the merge worked. This morning the user who first reported it wrote at 8:04 AM ET, "Woke up to my bots working this morning," and Colin then confirmed the fix reached every affected account.
Why it matters#
Anything those bots should have done since your merge didn't happen, including routine runs. The fix restores the bots going forward but does not replay what you sent while they were stuck.
How to use it#
- Open each bot you had before the merge and send it a short message, such as "hi." It should answer.
- Resend any request you made while it was stuck.
- In each bot's details pane, right-click a routine and choose Test to run it now, for any routine that should have fired since the merge.
- If a bot still sits on "Working on it…", reply in the forum thread with its name.
Example prompt to send each older bot once it answers:
List your routines that should have run since <merge date> and tell me which ones have no run since then, so I can test each one.
Good to know#
- Staff's fix note doesn't say whether missed routine runs are replayed. Treat them as missed.
- On Oct 13 staff asked people not to reset, delete or recreate the stuck bots. That advice is moot now, but if a bot is still stuck, keep following it and post in the thread.
What to watch#
Any reports of bots still stuck after the fix, and whether merges done from today on still need it.
