Expiring submissions

The Job Expire batch process changes submission jobs from New, Draft, or Quote status to Expired if they have passed an expiration threshold. In the base configuration, the batch process expires submission jobs with these statuses that are at least seven days past the effective date of the policy. The batch process, by default, runs every day at 6 A.M. as configured in the scheduler-config.xml file. The batch process expires all versions of a policy in a job that can be expired. If the policy version is already closed by being withdrawn, issued, or not taken, then it will not be expired.