Configuration

Core reads its settings from the host’s configuration file — slotd.conf on a hosted slot, stationd.conf on a station — when the extension is loaded at start-up. A key that is absent takes its default. A key whose value does not parse as its type also takes its default, and the host logs a warning naming it. A Boolean key is 1, true, yes or on, or 0, false, no or off, compared without regard to case — any other value, including a typo, is warned about and takes the default.

Comments go on their own line

The configuration parser treats everything after = as the literal value, so core.windowMaxSamples = 1000 # one thousand is not the number 1000 — it fails to parse and the default applies. Put comments on a line of their own.

---

Where a key is documented

Every Core key bounds exactly one operation, so each is documented on that operation’s page, next to the behaviour it changes. This page is the index.

Key	Bounds	Documented on
core.schedulerSecondsEnabled	Whether a Schedule may use 6-field (second-resolution) cron	Scheduler
core.maxSchedulerPerTask	How many Scheduler nodes one Task may hold	Scheduler
core.maxDelayPerTask	How many Delay nodes one Task may hold	Delay
core.windowMaxSamples	The largest count window a Window node may request	Window
logLineMaxBytes	Where a Logger line is truncated	Logger
logMemoryLines	How many log lines the in-memory ring holds	Logger

---

Per-Task caps

core.maxSchedulerPerTask and core.maxDelayPerTask are per-Task node counts, not rate limits: they cap how many nodes of that operation a single Task may contain. A negative value means unlimited, which is the default for both.

The cap travels to the editor as part of the operation’s schema, so the editor refuses to add the node that would exceed it rather than letting you build a Task the server will not accept.

---

Values for your plan

The numbers a hosted slot actually runs with are set per plan. This page gives the defaults the extension applies when a key is absent; the values in force for your plan are listed in the Acceptable Use Policy.