# Does ASP.NET App Unload Restarts/Stops HangFire?

**URL:** <https://discuss.hangfire.io/t/does-asp-net-app-unload-restarts-stops-hangfire/2241>\
**Category:** question\
**Created:** [July 26, 2016, 3:37am UTC](https://discuss.hangfire.io/t/does-asp-net-app-unload-restarts-stops-hangfire/2241 "2016-07-26T03:37:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mi.tran](https://avatars.discourse-cdn.com/v4/letter/m/b9bd4f/32.png) [@mi.tran](https://discuss.hangfire.io/u/mi.tran)\
**Post date:** [July 26, 2016, 3:37am UTC](https://discuss.hangfire.io/t/does-asp-net-app-unload-restarts-stops-hangfire/2241/1 "2016-07-26T03:37:31Z")

</div>

Hi,

For my [ASP.NET](http://ASP.NET) Web Application, I would like to use HangFire as a background worker for long running processes, as in below documentation link:  
[http://docs.hangfire.io/en/latest/background-processing/processing-background-jobs.html](http://docs.hangfire.io/en/latest/background-processing/processing-background-jobs.html)

But the processes I’m trying to get running can go from 3-7 hours.  
So the [ASP.NET](http://ASP.NET) app pool would recycle during that time (i.e. app unload).  
My question is how does HangFire “BackgroundJobServer” handle that scenario?  
Does it:

- Fail the job due to app pool recycle and retry it?  
(which wouldn’t work since it’d just have another app pool recycle again), or
- Continue working through the process, regardless of app pool recycle?