I’m running an Umbraco instance on Azure App Service using deployment slots. Both the production and pre-production slots share the same database. Webhooks are configured to clear the cache in a frontend application after content changes.
"Webhook": {
"Enabled": true,
"MaximumRetries": 5,
"Period": "00:00:10",
"EnableLoggingCleanup": true,
"KeepLogsForDays": 5
}
After deploying to either pre-production or production slot, webhooks are no longer triggered. I’ve observed this behavior across multiple instances. Occasionally, webhook execution resumes without any intervention.
In the logs, I see:
Completed stopping recurring background jobs hosted services
But I don’t see any indication that background jobs are restarted, and no webhooks are being fired. There are no related exceptions or errors in the logs.
What I’ve Tried:
Reviewed logs for exceptions — none found
Restarted the App Service — sometimes resolves the issue temporarily
Verified appsettings and webhook configuration — all looks correct
Expected Behavior:
Webhooks should fire consistently on content changes, even after deployments to either slot.
Environment:
Umbraco version: 13.6
Hosting: Azure App Service with staging slot
Shared database across slots
Webhooks configured via appsettings.json
Request:
Any insights into:
Why the recurring background jobs may not restart after deployments?
How to make webhook execution more reliable across slot deployments?