title: Quartz fails to delete a job, now what?
body: <p>Given a Quartz job and the following command</p>
  
  <pre><code>boolean deleted = scheduler.deleteJob(event.getName(), "some group name")
  </code></pre>
  
  <p>Assuming <code>deleted</code> comes back as <code>false</code>, as i understand it, it means that from the stand point of JVM, the job is still there.</p>
  
  <p>With this 2 questions:</p>
  
  <ol>
  <li>Is it possible to force delete a job?</li>
  <li>What event prevents Quartz to delete a job?</li>
  </ol>
  
  <p>If exception is not thrown, is it safe to assume that job was not found? What would cause this? Isn't the only way for this to happen is for the job to be deleted on the first place?</p>
  
  <p>I am using </p>
  
  <pre><code>    &lt;dependency&gt;
          &lt;groupId&gt;org.quartz-scheduler&lt;/groupId&gt;
          &lt;artifactId&gt;quartz&lt;/artifactId&gt;
          &lt;version&gt;1.8.0&lt;/version&gt;
      &lt;/dependency&gt;
  </code></pre>
  
  <p>Does this strike you as a correct way to handle things? Is my reasoning correct?</p>
  
  <pre><code>    boolean deleted;
      try {
          deleted = scheduler.deleteJob(event.getName(), "some group name");
          if (!deleted) {
              logger.warn("Quartz failed to delete the job!" + event.getName() + ". Job not found");
          }
      } catch (SchedulerException e) {
          logger.error("There is an internal Scheduler error", e);
      }
  </code></pre>