Facing an issue for off network apigee proxies
We have a redirect proxy where it is being called by our front-end consumers. But this redirect proxy is not referring to the latest revision of the target proxy even after deploying it to the environments. Any thoughts on this???? `APIProxy revision 51 of SYB-Ignite-transfers does not exist in environment dev of organization nonprod` -> this is the error. And revision 51 is not the deployed/latest one..
Answer by Nagashree B
·
Jun 21 at 08:59 PM
I have seen this issue a few times on the on-prem version of Apigee. This can happen if you have more than one message processors in your setup. The probable cause is a failure in deployment on one or more message processors.
Eg: When you deploy the proxy, it should be available on both the message processors - mp1 and mp2.However, if it failed on mp2 you may see the error when requests go to mp2
The only way I have seen this gets resolved is by restarting the message processors.
Reference to an older post for the same issue -
https://community.apigee.com/questions/59037/apiproxy-revision-xx-of-xxxx-does-not-exist-in-env.html
@Nagashree B Yes we did that and it worked. Thanks
