@Sungho Hong Welcome to the Microsoft Q&A forums.
From previous issues and experience, this error usually occurs in 2 scenarios
- When the system clock time is different from the one returned by the error message. Resolution: Please check if the system clock time (the machine from where the request is being made) and the time in the exception message are significantly different and update the system time. This is a requirement even if you are using the CosmosDB emulator.
- When a Read-Only key is used for Write operations Resolution: Please check if there are any instances where a ReadOnly Cosmos client is being wrongly used to make a write operation.
A few more scenarios are documented here
If these scenarios do not apply to you, please post the SDK version you are using, the region your CosmosDb is deployed in along with a few activity id's (from the response headers) and we can troubleshoot further.
----------
If an answer is helpful, please "Accept answer" or "Up-Vote" for the same which might be beneficial to other community members reading this thread.