Tenant type and model release lag
On the organization’s Tenant type page, organization admins set the model release lag per tenant type: whether the tenants of that type run the latest model release, or stay one or two releases behind. This is how you use staggered model releases.
To access the page, open the profile menu, select Organization settings, and select Tenant type. See Open Organization settings for who can open Organization settings.
Tenant types
Every tenant in an organization has a tenant type:
| Tenant type | Badge | Purpose |
|---|---|---|
Development |
Dev |
Working environment for building and debugging your integration. |
Testing |
Testing |
Testing before release. |
Production |
Prod |
Used by end users. |
All users see the badge next to the organization’s tenants in the tenant switcher.
Model release lag
For each tenant type, select a Model release lag:
-
Latest: tenants run the latest release of each model.
-
1 release behind: tenants stay one release behind the latest.
-
2 releases behind: tenants stay two releases behind the latest.
The default is Latest for every tenant type. Your change is saved as soon as you select a value.
The setting applies to all tenants of that tenant type, and to new releases of models on the platform. Timefold keeps the three most recent releases of a model. If a model has fewer older releases than the setting asks for, the tenant runs the oldest available release.
To check which model version a tenant runs, see Model version visibility in the UI.
Recommended setup
Timefold recommends Testing on Latest and Production on 1 release behind: your Testing tenant gets each new release first, so you can validate it with your own datasets before your Production tenant runs the release. See Staggered model releases for a worked example with version numbers.