Me
How does Start At / End At scheduling work for overrides?
Enki
I'll explain how the Start At / End At scheduling works for overrides based on the documentation.
**Source:** [Game Settings Configuration](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/2580021328/Game+Settings+Configuration)
## Start At / End At Scheduling Overview
The Start At and End At are **optional** fields that allow you to:
- Schedule overrides to go live in the future
- Avoid manually changing the override status to Active
### Key Details
- These fields are completely optional
- They help you pre-schedule when an override becomes active
- **Important:** When the End At date is reached, the system does **not** automatically revert the override's status
### Start Date Logic Visualization

### Scheduling Scenarios
1. **Only Start At Specified**
- Override becomes active at the specified start date
- Remains active indefinitely after that point
2. **Only End At Specified**
- Override is immediately active
- Remains active until the specified end date
3. **Both Start At and End At Specified**
- Override becomes active on the start date
- Remains active until the end date is reached
### Limitations
- No automatic status reversion when End At date is reached
- Manual intervention required to change override status after end date
### Best Practices
- Plan your override schedules carefully
- Set reminders to manually update override status if needed
- Regularly review and manage scheduled overrides
This scheduling mechanism provides flexibility in managing game configurations and ad settings across different time periods.