This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Log in to ask a question

Edge Router Routing to a Non Existent Revision API

Posted on 05-13-2019 03:56 AM
nathanaw
New Member
Reply posted on --/--/---- --:-- AM

Hi all, I deployed and redeployed an API Proxy. After deleting the API Proxy and redeploying it, when I call the API, it was routing to an non existent API (v7) when the current version deployed is V1.

I found that out when I checked the NGINX logs in the router logs. Is there any reason why v7 still exist when it no longer shows in the management console? How to purge/remove these old revision API proxies when one cannot see them in the console?

Thank you.

0 1 106
Topic Labels
0 Likes
1 REPLY 1

Posted on --/--/---- --:-- AM
nagashree_b
Silver 5
Silver 5
Reply posted on --/--/---- --:-- AM

@Nathan Aw

If you are using an on-prem version try restarting your message processors. We faced a similar issue and got it working after message processor restart.

0 Likes