To add a timed task to the ASP. Application, it must have been a thread that kept doing timed calculations, adding the quartz.net framework to its own ASP.
At night or the site after the no-access phase, the background scheduled threads and computing tasks are stopped, if you crawl the Application_End event, you will find that this event is actually called.
That must be the mechanism of application pool recycling for IIS in mischief. Because of IIS's default settings, if a site is in an application pool that has not been accessed or requested for more than a period of time, IIS automatically reclaims the program pool and kills the process. The quartz scheduled task also stopped automatically.
However, we can set the application pool parameters so that they are not automatically recycled (some cases cannot be avoided, such as a hot-deployed site, the number of errors overrun, etc.)
In the Find the application pool for this site, click "Advanced Settings ..."
In the list that opens, change the following settings:
Recycle--Fixed time interval (minutes) changed to 0
--Virtual/private memory limit (KB) changed to 0
Process Model-idle timeout (minutes) changed to 0
This way, in general, the program pool will not be automatically recycled, the background quartz scheduled tasks will work properly
IIS7 Application Pool Auto-recycle shutdown solution