Hey all - experiencing an issue with hosted targets that I have run out of debug options for. I deployed an API proxy hosted target revision yesterday around 6pm EST. I tested the single endpoint in the proxy and found it worked without issue. This morning, around 10am EST (16 hours after revision creation), I tested the single endpoint again with the same script and found that I was receiving a response from the initial "Hello World" revision, not the revision I deployed the previous day.
My best guess is that with zero load on the proxy over night it scaled down to zero instances, and when I tested this morning it scaled back up to a single instance to handle the call, but instead of deploying the latest revision's image it deployed the first revision's deployment.
This is at least the second time I have seen this behavior with the same proxy.
I don't see anything in the runtime or build logs that suggest any issues, though my latest attempt to fetch the logs errored out with "Error fetching Category Invalid status code from backend deployment service (403): Token has expired or not active yet." I have logged out and back in and am still getting the same error, so that is curious.
Has anyone seen this behavior before, with either a hosted target or the traditional proxy service with the Java runtime? If so, have you resolved it or did it resolve itself?
I recognize the hosted targets product is in beta so there may be some issues still to work out. Perhaps this is an issue in the product that needs reporting.
Thank you much.
LinkedIn
Twitter
