# Recurring jobs start too late

**URL:** <https://discuss.hangfire.io/t/recurring-jobs-start-too-late/4220>\
**Category:** question\
**Tags:** recurring\
**Created:** [January 6, 2018, 10:04pm UTC](https://discuss.hangfire.io/t/recurring-jobs-start-too-late/4220 "2018-01-06T22:04:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ferron\_Nijland](https://avatars.discourse-cdn.com/v4/letter/f/ac91a4/32.png) [@Ferron\_Nijland](https://discuss.hangfire.io/u/Ferron_Nijland)\
**Post date:** [January 6, 2018, 10:04pm UTC](https://discuss.hangfire.io/t/recurring-jobs-start-too-late/4220/1 "2018-01-06T22:04:41Z")

</div>

I use Hangfire within my .Net Core 2.0 application.  
I’ve set a recurring job to run every night at midnight.

But two nights ago it started at 6:53 and last night it started at 10:34.  
The application runs on a IIS 10 server.

Does anybody have a clue?

---

<div class="post-metadata">

**Author:** ![Ferron\_Nijland](https://avatars.discourse-cdn.com/v4/letter/f/ac91a4/32.png) [@Ferron\_Nijland](https://discuss.hangfire.io/u/Ferron_Nijland)\
**Post date:** [January 6, 2018, 11:06pm UTC](https://discuss.hangfire.io/t/recurring-jobs-start-too-late/4220/2 "2018-01-06T23:06:53Z")

</div>

Just now it went on time. Maybe something to do with IIS?