Disabled Functions on staging environment are fired after deployment

Question

Hi,

I have a Timer trigger function disabled on the staging environment and enabled on the live environment. When I deploy my app to the staging environment and swap it, the function is invoked on the staging environment right after the deployment (even though the timer is set to a different day/time and the function is disabled).

Answer 1

Hi @Nousha van Dijk (Q42) Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.

During a swap the setting from the target slot, which is production slot in your case, will be applied to source slot, i.e. staging slot. The applied settings include the following categories:

• Slot-specific app settings and connection strings (if applicable)
• Continuous deployment settings (if enabled)
• App Service authentication settings (if enabled)

You have an option to make the app settings as sticky before you perform a swap operation such that the settings do not get applied to other slots.

In addition to this, if you are using a ZipDeploy using Arm template, please validate that you are targeting the correct slot for deployment.

Please let us know if you still need assistance with this issue.