---
url: "https://www.skedulo.com/release-notes/optimization-recipes-schedule-jobs-whose-time-constraints-have-passed/"
type: "releaseNote"
title: "Optimization recipes: schedule Jobs whose time constraints have passed"
date: "2026-10-29"
productAreas: ["Web App"]
roles: ["Schedulers"]
platforms: ["Skedulo Pulse Platform","Skedulo On Salesforce"]
description: "A new Recipe setting lets optimization schedule Jobs whose time constraints have already passed, instead of leaving them unscheduled."
lastmod: "2026-10-29"
---

# Optimization recipes: schedule Jobs whose time constraints have passed

Published October 29, 2026

**Product areas:** Web App
**Roles:** Schedulers
**Platforms:** Skedulo Pulse Platform, Skedulo On Salesforce

A new Recipe setting lets optimization schedule Jobs whose time constraints have already passed, instead of leaving them unscheduled.

Optimization Recipes now include a **Schedule jobs whose time constraints have passed** setting. Previously, optimization left out any Job whose time constraints had all ended before the run, so overdue work had to be scheduled manually. With the setting on, optimization schedules these Jobs alongside the rest of the run.

This helps teams that use time constraints to track timeliness targets but still need to deliver every Job, including ones that have missed their target date.

**What's new**

- **Overdue Jobs are included:** Unscheduled Jobs whose time constraints all ended before the run can be placed anywhere in the run, with travel taken into account as usual.
- **Overdue Jobs get the highest priority:** When there isn't room for every Job, optimization favors overdue work.
- **Use with care:** Every overdue Job in the run's scope is included, however long ago its time constraints ended.

The setting is off by default, so existing Recipes behave as they do today.
