Changing jobs to expired status

A job in an Expired status indicates that it has been closed due to inactivity. An expired job is in a terminal state, and you cannot reopen it. However, you can clone an expired job into a new, open job.

The Job Expire batch process changes jobs from New, Draft, or Quote status to Expired if they have passed an expiration threshold. In the default configuration, the Job Expire batch process expires submission jobs with these statuses that are at least seven days past the effective date of the policy. In addition to submission jobs, you can enable expiration for other job types. You can configure the expiration threshold as the number of days past the effective date or the creation date.

Expiring jobs at an appropriate time can impact searching and reporting, and have a critical impact on business operations including purging and archiving. Select an expiration threshold that is consistent with the intended behavior of impacted business operations.

A job is expired after a sufficient and configurable interval of time has elapsed. A policy version can be expired when its status is either New, Draft, or Quoted. If the policy version is already closed by being withdrawn, issued, or not taken, then it will not be expired because it is already closed. When a policy version expires, its status changes to Expired. You can view the status in the Submission Manager screen or in the toolbar if you are in the submission wizard. An branch is not editable.