This is the first I have heard about this problem. Checking the API responses, I am seeing the following timestamps. Is it possible that something on your side is normalizing the response headers or returning cached responses? Or perhaps there was a previous issue I am unaware of that has since been resolved?
US: Last-Modified: Fri, 2 Dec 2022 17:15:16 GMT
EU: Last-Modified: Fri, 2 Dec 2022 17:33:59 GMT
KR: Last-Modified: Fri, 2 Dec 2022 17:33:59 GMT
TW: Last-Modified: Fri, 2 Dec 2022 17:27:53 GMT
By any chance are you using C# with the RestSharp library ?
I ask because recently we found a case in the API discord where this lib returns the Last-Modified in a separate subset of header fields and that lead to some confusion because you get both Date and Last-Modified from the API.
Perhaps some HTTP client library you use could be doing the same ? It should always have the Last-Modified tho.
I found out that the actual reason was that I had provisioned too little memory. So I had to split the commodity API out into a separate lambda with more memory Just forgot to update the thread with it. sorry.
I’m not sure why, but for some reason, I didn’t verify the URLs when I tested them individually to debug the issue I had. I found that in the method for manually updating one realm at a time, I forgot to authenticate, and for some reason, it did not throw an exception on 401…
I am actually using AWS Lambda with NodeJS with the Serverless framework . The issue was just me failing.