title: Quartz.Net job stops firing after several exceptions
body: <p>During a quartz job's execution, one of my activities may fail every time that it runs (every minute) for an hour or two because a dependent server is down for maintenance. I noticed that, when this happens, the job stops running and seems to unschedule itself without logging any exceptions that I can see. The job is still there as I have another job which runs and ensures that it is there with the assigned schedule I've given it, but the job itself ceases to execute. I'm assuming there's some threshold which removes a job which causes an exception x number of times in a row, but I'm hoping I can find a definitive answer for this. </p>
  
  <p>I'm trying to convince the main developer to catch the exception and log it instead of throwing a generic exception and letting it bubble up, but until then, researching the issue is all I can do.</p>
  
  <p>Here's the execution code, essentially. I also have the DisallowConcurrentExecution attribute set on the class itself. When this failure happens, it happens in less than 5 seconds, so I wouldn't expect that to come into play here:</p>
  
  <pre><code>    public void Execute(IJobExecutionContext context)
      {
          _logger.Log("Starting synchronization.");
  
          try
          {
              syncActivities();
          }
          catch (Exception ex)
          {   
              _logger.Log("Error. ", ex);
              throw;
          }
          finally
          {
              _logger.Log($"Completed synchronization.");
          }
      }
  </code></pre>