Duplicate Servers after ASP.Net Deploy

Has anyone had issues with duplicate Servers being listed after a deploy that updates an ASP.Net site? There are 2 different GUIDs identifying them in hangfire.[Servers] but they have the same Process Id. It takes us restarting the IIS server process for this to resolve.

I had same issue too. Initialize new BackgroundJobServer() instance on application_start in global.asax and Dispose that instance on application_end

Yeah. I’m already following the hangfire guidelines for always running in IIS. So we’re already doing that.

Strangely enough, we have a beta version of the site on the same server in a different app pool and it doesn’t have this issue. It’s usage is far lower though and the app pool recycles due to inactivity, i’m following that lead now.