NodeJS Call Cancelled uncaught exception when making call to zitadel API
So I've noticed an issue where one of our nodejs services using the js sdk ends up restarting the container and killing the pod on kubernetes. See screenshot for the issue.
It's intermittent, it's happening infrequently, and primarily after prolonged inactivity in the pod (overnight for example).
Since it's an uncaught exception it's causing istio to issue a 503 back to the client caller, as the upstream target to the proxy is understandably and justifiably dead (issuing TCP RST packets before the pod dies).
Any thoughts?
It's intermittent, it's happening infrequently, and primarily after prolonged inactivity in the pod (overnight for example).
Since it's an uncaught exception it's causing istio to issue a 503 back to the client caller, as the upstream target to the proxy is understandably and justifiably dead (issuing TCP RST packets before the pod dies).
Any thoughts?
