title: Sql Job running for 30 minutes then report successful
body: <p>We have a job that runs every night and rebuild the indexes on a customer database, however after installing the job, it runs successfully every night according to the history and finishes in around 30 minutes every night, however we found that the indexes that it should fix, are not actually fixed and still fragmented above the allowed level.</p>
  
  <p>Is there anything that would stop a job from running more then 30 minutes? It currently doesn't have an end date on it.</p>