Share via

Teams Meeting Side Panel app shows “Conversation was not found (404)” next day — is this a known issue?

Irshad Gouri 60 Reputation points
2025-12-11T05:42:14.4866667+00:00

Hi Team,

I am developing a Microsoft Teams Meeting Side Panel app using this sample: https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/meetings-sidepanel/nodejs

Everything works perfectly on the same day when I run my app. I have also made the content URL static, and the meeting extension loads fine.

But next morning, without making any changes, I start getting the following error:

{errorCode: 404,…}
errorCode: 404
message: "{\"errorCode\":404,\"message\":\"Conversation was not found\",\"subErrorCode\":\"RequestHandlerException\"}"
standardizedError: {
   errorCode: 404,
   errorSubCode: 1,
   errorSubCodeString: "RequestHandlerException",
   errorDescription: "RequestHandlerException-Conversation was not found"
}

Once this error starts, the side panel stops working completely. The only workaround I have right now is:

  • Create a new Teams app again

Reinstall it

Re-add it inside the meeting

Then it works for that day, but the next day the same 404 issue appears again. Since I'm actively developing, it becomes impossible to test because I need to recreate the entire app package every morning.

My Questions

Is this a known glitch/bug on the Microsoft side for meeting extensions or conversation references?

Why does the same side panel app run perfectly on the same day, but fails with “Conversation was not found” after some hours?

Does the meeting conversation or thread ID expire daily in development mode?

Is there any stable way to keep the meeting extension working across days without recreating a new Teams app every time?

Additional Info

Using Bot Framework (Node.js sample)

No code changes between “working day” and “next morning”

Only the conversation reference seems to become invalid overnight

Please help me understand whether this is expected behavior or a bug. Thanks in advance!

Microsoft Teams | Development
Microsoft Teams | Development
Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-12-11T05:42:36.27+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The issue you're experiencing with the "Conversation was not found (404)" error in your Microsoft Teams Meeting Side Panel app may be related to how conversation references are managed in Teams. Here are some insights into your questions:

    1. Known Glitch/Bug: While there isn't specific documentation indicating this is a known bug, the behavior you describe could stem from how Microsoft Teams handles conversation references. It is possible that the conversation context is lost after a certain period, especially if the meeting is no longer active.
    2. Daily Functionality: The fact that your app works perfectly on the same day but fails the next morning suggests that the conversation reference may indeed be expiring or becoming invalid after a period of inactivity. This is not uncommon in systems that manage state and context over time.
    3. Expiration of Conversation ID: Yes, it is likely that the meeting conversation or thread ID does expire, particularly in development mode where sessions may not be maintained as they would be in a production environment.
    4. Stable Operation Across Days: To maintain the functionality of your meeting extension across days without needing to recreate the app, consider implementing a mechanism to refresh or re-establish the conversation reference when the app is loaded. This could involve checking the current state of the conversation and reinitializing it if necessary. Additionally, ensuring that your app handles the 404 error gracefully and attempts to recover could improve your development experience.

    If you continue to face issues, consider reaching out to Microsoft support or the developer community for further assistance, as they may have more insights into this specific behavior.

    References:

    0 comments
  2. Kudos-Ng 10,550 Reputation points Microsoft External Staff Moderator
    2025-12-11T13:43:10.7033333+00:00

    Hi Irshad Gouri,

    Thank you for posting your question in the Microsoft Q&A forum. 

    Based on your description, I’ve reviewed the expected behavior for Teams meeting side panel apps and, at this time, I haven’t found any officially reported incidents that match what you’re seeing exactly.

    To better understand your situation, could you please share a few additional details:

    • Runtime context: Are you calling microsoftTeams.app.getContext() on side-panel load and logging chatId, meetingId, and frameContext? The next morning, does the chatId you log differ from the one recorded the previous day?
    • Are you persisting the bot conversation reference (e.g., in Cosmos DB/Redis), or is it kept in memory only?
    • Does the side panel UI load successfully (i.e., contentUrl is fine), but posting to the meeting chat via the bot returns 404? Or does the contentUrl fail to load?
    • Does the error occur immediately when the app opens, or only when your code calls Bot/Graph APIs?

    Looking forward to your input.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.