Whenever I try to create a new post while I already have a draft saved, I get the message:
“Draft is being edited in another window. Please reload this page.”
Here’s what’s happening:
When I click Reload, the page refreshes and takes me to the Home page. My previous draft is still present and intact, but I’m not able to proceed with creating a new topic directly.
When I click Ignore, it lets me continue, but it completely overwrites the existing draft with the new content or wipes it out entirely.
This behaviour feels restrictive because:
I cannot create multiple drafts.
The Ignore option is misleading — instead of letting me proceed with the new topic independently, it causes the older draft to be lost.
Has anyone else experienced this?
Is this the expected behaviour? A workaround would be helpful.
Thanks for addressing this and sharing your experience @MortenCopenhagen
Even if only one draft is allowed in this case, that’s fine. The issue is the pop-up, the “Ignore” button is misleading because it ends up deleting/overwriting the draft without warning.
Hoping @AngieYC can clarify the expected behaviour and possible fix.
When I hit Reply, another message showed up, saying that I already posted a very similar reply. But I did reload and saw checked it was not already posted.
My guess is this happens when there is a temporary disruption in the network connectivity that we do not notice, but the Connect website probably does and goes into offline mode with this weird message.
The problem is mainly caused by a momentary network/connection interruption that is often unnoticeable.
When you see a red triangle with an exclamation mark (the “Warning” icon) or the message “Draft offline,” it means your connection is interrupted. Depending on what you’re doing, you might also see other messages pop up.
We’re aware that the pop-up messages might be confusing, even after our explanation. We’ll take this feedback internally and work on improving the experience for everyone on Connect.
In your case @EshaHarish, when you are seeing the pop-up message you shared, selecting “Ignore” is currently the correct choice.
As for @MortenCopenhagen, Just ignore the pop-up and hit reply again to post. The team is looking into this, in case of any edge cases.
I’ll pin my reply to the top so others with similar issues can see the current answer. I’ll keep you all updated if there are any more developments.
Thank you so much for looking into this and for the detailed explanation @AngieYC
I really appreciate the effort
From what I’ve observed, when I click Ignore, it lets me continue, but it often overwrites my existing draft or wipes it out entirely. On the other hand, when I click Reload, the page refreshes and takes me back to the Home page, but my previous draft stays intact, even though I can’t directly continue creating a new topic from there.
Based on this, Reload feels like the safer option for me to avoid losing my draft abruptly.
Could you please confirm if choosing Reload is indeed the recommended or safer approach until the issue is fully resolved or kindly correct me if I’ve misunderstood anything?
Thanks again for your support and for keeping us updated.
If you have an ongoing draft then yes, “reload” is the better option until you successfully post your draft.
This pop-up message appears when you try to create or reply to a topic/post when you haven’t closed the composer window. It serves as a notification to remind you that you have an existing composer window open.
Thank you for clarifying!
If have an ongoing draft, I’ll continue choosing Reload as the safer option.
Thanks also for explaining that the pop-up appears due to an open composer window, that really helps.
Thanks @AngieYC. As you know in early August I reported the issue that @EshaHarish reports here. My experience is similar to @MortenCopenhagen’s where the pop-up continues to be redisplayed after selecting ignore. While the team’s finings are that this is mainly caused by unnoticeable momentary network/connection interruptions, it’s strange that this does not interrupt other sites that I am working on at the time of the issue is encountered on Connect.
