Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
Web App (Linux): Deployment Slots Swap Causes Traffic to Precede Startup Signal
Problem description
I am experiencing an issue where, during deployment slot swaps in my Azure Web App (Linux), traffic begins before the startup signal is issued. This results in some instances serving traffic prematurely, which is causing errors and inconsistent behavior. I need assistance understanding why this is happening and how to prevent traffic from starting before the startup signal.
Environment
Azure Web App (Linux), Deployment slots, Region not specified in the case information.
What I've already tried
I have reviewed the latest case communication and logs, but I have not tried any troubleshooting steps myself yet.
Current status
I am seeking guidance on the cause of this behavior and how to ensure traffic only begins after the startup signal during slot swaps.