Copilot Update Glitch: Immediate Daily Chat Limit and Missing History (Sept 8th Update

Question

Copilot Update Glitch: Immediate Daily Chat Limit and Missing History (Sept 8th Update

D D 0

Hello,

I am posting to report a major bug with the recent Microsoft Copilot update that occurred on September 8th around 2:00 PM - 3:00 PM Eastern Time. Immediately following this update, two severe issues occurred simultaneously on my free Microsoft account:

IDaily Chat Limit Glitch: Even though I am on a free account with standard daily allowances, the system is cutting me off almost immediately. Yesterday, it hard-blocked me with a "daily chat limit reached" error after almost no usage. This morning, I was able to ask just a few quick questions, but I had to cut my session short and stop using it entirely out of fear that it would trigger the exact same premature lockout. This happens across the Windows app, standard web browsers, and Incognito mode.
Missing Chat History: My most recent chat threads completely vanished from my history sidebar right after the update took place.

I have already contacted Microsoft Support, and they confirmed they cannot manually escalate the issue because it is a free account. However, this is clearly a widespread backend profile data corruption or token synchronization failure caused directly by the September 8th update patch, rather than standard free-tier limits or high server traffic.

I have an official support Case ID # Moderator note: PII removed on file for this session.

Are other users experiencing this exact same rollout glitch from yesterday afternoon? Has anyone found a way to force the backend server to re-sync the account history and usage tokens, or do we have to wait for an engineering cloud patch? Any visibility from a Microsoft agent or community moderator would be greatly appreciated.

Glen Smith 1 Reputation point

2026-09-11T12:15:00.3033333+00:00

Mine updated today and lost some chat history. 2 questions in about the chat locations and reached daily limit
Katalin baranyai 0 Reputation points

2026-09-18T14:52:17.8433333+00:00

Hello! I can't use a copilot chatbot in the app anymore. It's important. Please help.

7 answers

Your answer

Glen Smith 1 Reputation point

2026-09-11T12:15:00.3033333+00:00

Mine updated today and lost some chat history. 2 questions in about the chat locations and reached daily limit
Katalin baranyai 0 Reputation points

2026-09-18T14:52:17.8433333+00:00

Hello! I can't use a copilot chatbot in the app anymore. It's important. Please help.

Answer 1

Bug Report: Copilot Quota Lockout following September 8th Update (Account Token Failure & Database Timeout).

Update as of: 09-27-2026

Connected to 2 Support Tickets (Available on request).

The global sync patch has NOT resolved my issue.

The app is failing to link my profile and shows a generic greeting instead of my name 'D'. Note: The app UI displays my account name in the lower corner, but the backend fails to link or acknowledge my identity during the session handshake.

I have already attempted a full log-out and clean log-in in a fresh browser session, but the issue persists.

Attempting to load the most recent thread results in an immediate server timeout and the 'Click new topic' error.

The backend is completely failing to authenticate my account.

Answer 2

Emma1-N 13,320 Microsoft External Staff Moderator

Welcome D D,

Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

Thank you for providing the detailed information.

Based on your description, the issue appears to affect both chat history synchronization and usage-limit tracking across multiple devices and browsers, which makes a local device issue less likely. Similar reports from other users have recently described missing Copilot conversation history and synchronization errors after updates.

There is currently no documented user-facing option to force a backend resynchronization of Copilot chat history or usage counters. Microsoft documentation indicates that conversation history is normally associated with the signed-in Microsoft account and should be available across Copilot experiences when synchronization is functioning correctly.

To better understand the scope of the issue, could you confirm:

Do you see any synchronization-related message, such as "Chats and content couldn't finish syncing"?
Are the missing conversations absent on all devices, including Copilot on the web?
Does the daily chat-limit behavior occur every day, or only since the September 8 update?

The additional details may help determine whether this is an account-specific synchronization issue or part of a broader service-related problem.

Looking for your update.

D D 0 Reputation points

2026-09-10T10:45:55.0666667+00:00
Thank you for the update. To answer your questions so this can be escalated to the engineering team:

Synchronization messages: Yes, I saw a sync error on the day of the update (September 8th). None since. No, I do not see an error message, it just said I hit the daily limit despite being signed in. I haven't chatted very long since so I don't hit the error again.

Cross-device behavior: The history is missing and the daily limit error occurs across all my devices, including Copilot on the web, confirming it is an account/backend issue and not a local device problem.

Timeline: This daily chat-limit behavior started immediately after the September 8 update. Prior to this update, I had no daily chat limits while signed into my account.

Since this began precisely with the September 8 deployment and affects multiple devices, please escalate this to the backend team as a broken account-token or quota-tracking bug introduced in the latest update.
Emma1-N 13,320 Reputation points Microsoft External Staff Moderator

2026-09-11T07:59:16.68+00:00

Hello D D,

If the history is still missing everywhere, continue updating your existing Microsoft Support case with these findings. Based on what you've described, an account-level investigation would be more appropriate than additional device troubleshooting.
D D 0 Reputation points

2026-09-11T11:19:32.9666667+00:00

Update on Sync Behavior: The chat history has successfully synchronized and is visible on multiple physical machines and the web interface, proving the local client is communicating with the server.

Database Timeout: Clicking any synchronized chat causes an indefinite loading delay. It eventually times out, fails to render content, and forces a "new thread" prompt. This happens even on a threat just created prior to the update which was new.

Persistent Quota Restriction: Daily chat limits are still active across all sessions, indicating the backend account flag is corrupted or stuck in an unauthenticated profile status.

Request: Please escalate this to tier-2 engineering to run a backend user profile data-index rebuild and clear the stuck session tokens on the server side.
Emma1-N 13,320 Reputation points Microsoft External Staff Moderator

2026-09-12T08:38:30.01+00:00
Hello D D,

Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. Our role is limited to providing technical guidance on reported issues, requests, or ideas. The best next step is to update your existing Microsoft Support case with these new findings.

Please follow the steps below to connect with Live Chat Support.

Visit the Microsoft Support contact page: Contact - Microsoft Support

In the search bar provided on the page, type "daily chat limit" and press Enter.

Click on the "Get Help" button that appears.

Scroll down the page until you see and click on the "Contact Support" option.

When prompted to select your product or service, choose "Other Products".

For the category, choose "Windows".

Look for and click on "Chat with a support agent in your web browser".

When prompted, provide a valid contact email where Microsoft can reach you regarding your case.

Explain your situation clearly: Be concise but provide all the relevant details.

Thank you for your understanding.
D D 0 Reputation points

2026-09-16T10:51:14.95+00:00

The global sync patch has NOT resolved my issue.

The app is failing to link my profile and shows a generic greeting instead of my name 'D'. Note: The app UI displays my account name in the lower corner, but the backend fails to link or acknowledge my identity during the session handshake.

I have already attempted a full log-out and clean log-in in a fresh browser session, but the issue persists.

Attempting to load the most recent thread results in an immediate server timeout and the 'Click new topic' error.

The backend is completely failing to authenticate my account.
fli men 0 Reputation points

2026-09-18T11:22:02.0566667+00:00

Hi Emma1-N and everyone,

I’m experiencing the same issue described by D D. After only a few text prompts, both on the mobile app and on the desktop/web version, I start receiving the “daily limit reached” message, even though I haven’t had this problem before.

Chat history synchronization itself seems to be working correctly: my previous conversations appear across devices as expected. The problem is specifically with the usage counter: after just a handful of exchanges in a day, Copilot tells me I’ve hit the daily limit.

Could you please confirm whether this behavior is now part of the latest Copilot version (for example, a reduced free quota or a new limit policy), or if it’s likely a glitch in the system? If it’s intentional, any official documentation or announcement about the new limits would be very helpful.

Thank you in advance for your support.
Katalin baranyai 0 Reputation points

2026-09-20T10:44:47.3+00:00

Nekem is bizonyos idő utan le tilt, terjek vissza

MAGYAR idő szerint hajnal 2 orakkor. Nem enged kerdezni egy adott témaban. Please Help!

Answer 3

Bug Report: Copilot Quota Lockout following September 8th Update (Account Token Failure & Database Timeout).

Update as of: 09-24-2026

Connected to 2 Support Tickets (Available on request).

The global sync patch has NOT resolved my issue.

The app is failing to link my profile and shows a generic greeting instead of my name 'D'. Note: The app UI displays my account name in the lower corner, but the backend fails to link or acknowledge my identity during the session handshake.

I have already attempted a full log-out and clean log-in in a fresh browser session, but the issue persists.

Attempting to load the most recent thread results in an immediate server timeout and the 'Click new topic' error.

The backend is completely failing to authenticate my account.

Answer 4

Bug Report: Copilot Quota Lockout following September 8th Update (Account Token Failure & Database Timeout). Connected to 2 Support Tickets (Available on request)

Update as of: 09-22-2026

The global sync patch has NOT resolved my issue.

The app is failing to link my profile and shows a generic greeting instead of my name 'D'. Note: The app UI displays my account name in the lower corner, but the backend fails to link or acknowledge my identity during the session handshake.

I have already attempted a full log-out and clean log-in in a fresh browser session, but the issue persists.

Attempting to load the most recent thread results in an immediate server timeout and the 'Click new topic' error.

The backend is completely failing to authenticate my account.

Answer 5

D D 0

Bug Report: Copilot Quota Lockout following September 8th Update (Account Token Failure & Database Timeout). Connected to 2 Support Tickets (Available on request)

Update as of: 09-19-2026

The global sync patch has NOT resolved my issue.

The app is failing to link my profile and shows a generic greeting instead of my name 'D'. Note: The app UI displays my account name in the lower corner, but the backend fails to link or acknowledge my identity during the session handshake.

I have already attempted a full log-out and clean log-in in a fresh browser session, but the issue persists.

Attempting to load the most recent thread results in an immediate server timeout and the 'Click new topic' error.

The backend is completely failing to authenticate my account.

A 0 Reputation points

2026-09-23T02:18:50.9066667+00:00

Im having the exact same issues. I keeps getting notifications saying "You've reached your daily limit. Get more usage now or check back at 7:00 PM." I get this after one use. I dont understand how to fix or why it even happened.