- Overview
- Getting Started
- Quick Start Guide
- Core Concepts
- Users
- Models
- Creating a Model
- Model Card
- Creating a Release
- Uploading Files
- Uploading Images
- Model Templating
- Data Cards
- Creating a Data Card
- Managing Data Cards
- Using a Model
- Browsing the Marketplace
- Requesting Access
- Using a Pushed Docker Image
- Downloading Files
- Reviews
- Understanding Reviews
- Reviewing
- Reviewing a Release
- Reviewing an Access Request
- Reviewing a Model Card Lifecycle
- Review Outcomes
- Security Scanning
- File Scanning
- Image Scanning
- Inferencing
- Creating an Inference Service
- Managing Inference Services
- Model Mirroring
- Creating a Mirrored Model
- Editing a Mirrored Model Card
- Untrusted Models
- Untrusted Models
- Deletion
- Deleting a File
- Deleting a Model
- Soft Deletion
- Programmatic Access
- Authentication
- Personal Access Tokens
- Python Client
- OpenAPI Reference
- Webhooks
- Administration
- Getting Started
- Deployment Architecture
- App Configuration
- Model Lifecycle Configuration
- Schemas
- Understanding Schemas
- Create a Schema
- Upload a Schema
- Schema Migrations
- Review Roles
- Managing Review Roles
- Assigning Roles to Schemas
- Federation
- Peer Integration
- Microservices
- Artefact Scanners
- Helm
- Basic Usage
- Configuration
- Isolated Environments
- Migrations
- Bailo v0.4
- Bailo v2.0
- DataBase Scripts
- Reference
- Glossary
- Roles & Permissions
- Troubleshooting & FAQ
Model Lifecycle Configuration
Bailo includes configurable lifecycle reminder functionality to help ensure that models are periodically reviewed and remain compliant with organisational governance policies. The system can automatically send reminder emails to model owners before and after a lifecycle review due date.
Retention behaviour is controlled through the SMTP lifecycle configuration. This determines when reminder notifications are sent and how frequently overdue reminders are repeated.
This page explains how to configure lifecycle reminders, how the reminder and warning flows work, and how to safely disable the feature if required.
Common questions this page answers:
- How do I configure the lifecycle rules?
- What are the configuration options?
Configuration Location
Lifecycle reminder behaviour is configured in the Bailo backend configuration under smtp.lifecycle.
Example configuration:
smtp: {
enabled: true,
lifecycle: {
preReminderIntervals: ['1 day', '2 weeks', '10 weeks'],
postReminderInterval: '1 day'
}
}
Configuration Options
smtp.lifecycle.preReminderIntervals
A list of time intervals before the lifecycle review due date when reminder emails should be sent.
Example:
preReminderIntervals: ['1 day', '2 weeks', '10 weeks']
This example produces:
- A reminder 10 weeks before the due date
- A reminder 2 weeks before the due date
- A reminder 1 day before the due date
Supported formats follow the human-interval syntax, such as:
1 hour12 hours1 day3 days2 weeks1 month
For more information please read Human Interval.
If an interval cannot be parsed, Bailo logs a warning and skips that interval.
Important behaviour:
- Reminders are only scheduled if the calculated timestamp is in the future
- If a lifecycle review is created close to its due date, earlier reminders may be skipped automatically
smtp.lifecycle.postReminderInterval
Defines how often reminder emails are sent after the lifecycle review due date has passed.
postReminderInterval: '1 day'
Behaviour:
- After the due date, Bailo sends reminder emails repeatedly at the configured interval
- These reminders continue until the lifecycle review is completed or removed
Supported formats follow the same human-interval syntax used by preReminderIntervals. If the interval cannot be parsed, Bailo logs a warning and no post‑due reminders will be scheduled.
Related pages
- Model Lifecycle - Completing and updating model card lifecycle reviews
Copyright © Crown Copyright 2026.
