Forum Discussion

Kimchhun's avatar
Kimchhun
Copper Contributor
Mar 25, 2026

Error ColdStoreNotSupportedForMessageException when sending message MS Teams via Graph API.

I'm using the Graph API to send a message to a Microsoft Teams channel, but I'm getting the following error.

Endpoint: https://graph.microsoft.com/v1.0/teams/{team_id}/channels/{channel_id}/messages

Reference: https://learn.microsoft.com/ja-jp/graph/api/chatmessage-post?view=graph-rest-1.0&tabs=http#http-request

 

Error response:

{
  "code": "NotFound",
  "message": "NotFound",
  "innerError": {
    "code": "1",
    "message": "MessageNotFound-Message does not exist in the thread: ColdStoreNotSupportedForMessageException:ColdStoreMessageOperations is not supported if cutOffColdStoreEpoch is not provided. (msgVersion:1773201279001, cutoff:1773137924398)",
    "date": "2026-03-17T10:18:44",
    "request-id": "7e4d1acd-05d0-4ff6-82ac-4cf0549bfa56",
    "client-request-id": "7e4d1acd-05d0-4ff6-82ac-4cf0549bfa56"
  }
}

 

I couldn't find any documentation related to ColdStoreNotSupportedForMessageException. Has anyone encountered this before or have any insight into what's causing it?

microsoft teams

3 Replies

  • Kimchhun's avatar
    Kimchhun
    Copper Contributor
    Mar 26, 2026

    Hello Nivedipa-MSFT​ - Thanks for the response.

    It's a reply. I verified on my end that endpoint (I posted incorrect endpoint) and message-id are correct.

    Could you please let us know in what scenario this leads to a ColdStoreNotSupportedForMessageException, and if there is any documentation related to the required internal parameters (cutOffColdStoreEpoch)?

    I believe this could be a backend issue or an edge case, as the same code has been running for quite some time without any issues. Please refer to the information in error response attached in above post for the request ID and timestamp for further investigation.

    • Nivedipa-MSFT's avatar
      Nivedipa-MSFT
      Icon for Microsoft rankMicrosoft
      Apr 08, 2026

      Hello Kimchhun - Apologies for the delay response.

      A ColdStoreNotSupportedForMessageException occurs when an API call tries to access or modify messages that have been moved to cold (archived) storage, typically because they are older than the active retention period.

      • The cutOffColdStoreEpoch is an internal Teams setting that determines the boundary between hot and cold storage. It is not publicly documented and cannot be changed by developers or tenants.
      • This exception often arises when using the Graph API to work with older messages, when bots reference past conversation activities, or during compliance exports involving tiered storage.

      Recommendation: To address this, handle the exception gracefully and avoid attempting to update or delete messages outside the retention window. If possible, provide details about the specific API call and the age of the affected messages.

  • Nivedipa-MSFT's avatar
    Nivedipa-MSFT
    Icon for Microsoft rankMicrosoft
    Mar 25, 2026

    Hello Kimchhun - Thanks for bringing this issue to our attention. 

    The “cold store” error typically occurs when your request is handled as if it should operate on an existing thread or message—such as in a reply or parent-message scenario—but the required internal parameter (cutOffColdStoreEpoch) is missing and cannot be set via Graph. 

    Here’s how to address it quickly:

    • To post a new top-level message, ensure you’re using the correct endpoint (without {message-id}):
      POST /teams/{team-id}/channels/{channel-id}/messages and include at least body.content. 
    • If replying to a message, use:
      POST /teams/{team-id}/channels/{channel-id}/messages/{message-id}/replies and verify that {message-id} is valid. 
    • If the error persists even with a minimal payload (just body.content) and correct IDs, it may be a backend issue or an edge case. Please provide the request ID, timestamp, and tenant ID for further investigation.