Downtime takes some or all of a resource's units out of service for a period: a van in the shop, a boat hauled out for the winter. Departures in that window lose those units right away, so they sell fewer seats or stop selling.
Owners, Admins, Managers, and Users can record downtime.
Add downtime
Go to Settings → Operations → Resources and select Edit next to the resource.
In Downtime, select Add downtime.
Set From and Until. Times are in your workspace's time zone.
Set Units out of service: how many of the pool's units are out. A resource with a single unit skips this field, since the whole resource is out for the period.
Add a Note if it helps, such as "Annual service".
Select Create.
Use Edit or Delete on an entry to change or remove it. Downtime counts as soon as you save it; there is no approval step.
What happens next
Departures that overlap the downtime, plus the resource's turnaround, lose those units immediately. Travelers see fewer seats, or none, and nothing about the resource itself.
If an upcoming departure already has more booked than the resource can now carry, you see a warning such as "2 upcoming departures now exceed Minibus" with an Open calendar link, and teammates who receive Resource conflicts alerts get it in their notification bell. Nothing is canceled or resized for you.
If departures only stop selling, or sell fewer seats, only you are told, with a link to the departure or the calendar.
Downtime never blocks you. You can still book a departure over its resources on purpose; travelers cannot.
Can I set downtime that repeats every week?
Can I set downtime that repeats every week?
No. Each entry is a one-off window. Add a separate entry for each period.