Can't access second API when first was recently used within same APIM service

Question

Can't access second API when first was recently used within same APIM service

Oleksandr Yakovliev 25

I have two APIs in my APIM service. Each API endpoint has running Open AI service behind. When I'm using first endpoint (in my AI chat app) with one model deployed - everything is ok, but after that when I try to use another model in my chat app (I can switch between them in runtime) I'm receving an error from APIM service:

 "error": {
        "code": "DeploymentNotFound",
        "message": "The API deployment for this resource does not exist. If you created the deployment within the last 5 minutes, please wait a moment and try again."
    }

After some time when I start working with second endpoint and switch to first one - same error. Seems like APIM service is switching between these two APIs but can't handle both at the same time. How can I reconfigure APIM service to work with each API at the same time? APIM service has Basic tier

Accepted answer

0 additional answers

Your answer

Answer 1

Pravallika Kothaveeranna Gari 955 Microsoft External Staff Moderator

Hi Oleksandr Yakovliev,

Check if below steps helps to resolve the issue:

Double-check Deployment Names for both models and ensure they are correctly referenced in your APIM service.
Verify if both models are deployed correctly. After deploying a new model, wait for at least 5 minutes before switching to it in your chat app.
Upgrade Open AI version.
Check backend configurations and make sure APIM is correctly routing requests.
Ensure that the API Management service isn't caching or holding onto the previous deployment state when switching between models.
Consider upgrading to a higher tier such as standard or Premium if your requirements exceed the Basic tier's capabilities.

Pravallika Kothaveeranna Gari 955 Reputation points Microsoft External Staff Moderator

2025-03-14T03:41:51.9233333+00:00

Oleksandr Yakovliev, Just checking in to see if the provided answer helped. If it did, please click "Accept the answer” and Yes for the answer . So it can benefit other community members reading this thread. If you have any further queries, do let us know.
Oleksandr Yakovliev 25 Reputation points

2025-03-15T08:01:34.5533333+00:00

The problem was in load balancing logic applied to inbound policy. Both APIs were using the same variable name for listing backends.

Share via

Can't access second API when first was recently used within same APIM service

0 additional answers

Your answer