Parameter:
BUSYTIME_LIMIT_SETTINGSShort description: Limits the time window that Calendar/Free-Time lookups read back from
busytime.nsf, and therefore the response size per request.Profile
Parameter | BUSYTIME_LIMIT_SETTINGS |
Category | Mail / Router |
Component | Server |
Available since | 9.0.1 |
Supported versions | 9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | Configuration document (Calendar & Scheduling) |
Possible values | min,max (days); typically e.g. 30,180 |
Description
Free/Busy queries from the Calendar run against
busytime.nsf (or the cluster equivalent clubusy.nsf). Without a limit, clients can request time windows spanning several years – this produces huge responses and CPU load. BUSYTIME_LIMIT_SETTINGS defines a day interval (min/max) outside of which lookups are rejected or limited.Example configuration
BUSYTIME_LIMIT_SETTINGS=30,180
Notes & pitfalls
- Value in days.
- For Outlook iCal sharing, 90–180 is often a good fit, otherwise 30–60 is usually enough.
- Complements
BUSYTIME_TASK_INTERVAL(refresh interval).
- Values that are too narrow can lead to missing free-time suggestions for recurring meetings.
- The change takes effect after a restart of the
Sched/Calconntask or after a server restart.