question

SteveFeidelberg-4040 avatar image
0 Votes"
SteveFeidelberg-4040 asked John-6522 published

After Swap Azure Function with CosmosDBTrigger Continues Firing On Slot that was Swapped Out

I've got a function app that is configured as follows:


In production using Azure release pipeline I deploy a new version as follows:

  1. Deploy new version of code to slot

  2. Wait for StatusCheck to return isRunning = false

  3. Swap


Actual: The staging slot (i.e. that now has the "old" code) takes over. More specifically the CosmosDBTrigger on the staging slot appears to be "stealing" the Cosmos updates. If I stop the staging slot then the CosmosDBTrigger on the production slot wins out.

Expectation: That the production slot (i.e. the one with the "new" code) takes over without having to stop the staging slot

Am I missing anything here is there any configuration I need to modify to get the production slot (i.e. new code) CosmosDBTrigger to take over. I would assume the same type of deal applies to other triggers as well.

Thanks





azure-functionsazure-cosmos-db
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@SteveFeidelberg-4040 Thank you for the question. We will review and update at the earliest.

0 Votes 0 ·

1 Answer

John-6522 avatar image
0 Votes"
John-6522 answered John-6522 published

Lol, 10 months and no feedback? Did you find any solution to this issue?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.