Forum Discussion
Error ColdStoreNotSupportedForMessageException when sending message MS Teams via Graph API.
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.
MicrosoftHello 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.