Some api calls return status 304 for no reason, but fixed magically after re-deploy

Hey guys,

Some of our api calls return 304 on render logs, even though the browser client reports 200 response to them.

I can’t see any reason from the codebase this should happen, becuase we don’t have a single service that return this error code.

Furthermore, everytime it happends, when I trigger deployment manually this issue is magically get fixed.

This really annoing and add significant downtime to every deployment.

Hi @grmmph,

I did some digging and I wasn’t able to see anything that would generate a 304 response on our end but a 200 response on the client’s end. Can you share an example of the logs you are seeing and any steps to reproduce this issue?