I've encountered a problem when I deploy changes to a Shared Flow that's used in a Flow Hook.
It seems that if I do not create a new revision then previous deployments of that Shared Flow are still active in addition to the latest deployment. Apigee will just load balance across old and new deployment of the Shared Flow, so every time I call my API I see different Flow Hook behavior in the trace window.
The issue goes away if I create a new revision and deploy it.
Is this behavior expected, and if so is it documented anywhere?
LinkedIn
Twitter
