Settings
The Settings page contains the global configuration for your Runner installation. All settings here apply system-wide and require the Admin role to change.
General
Version — shows the currently running Web and API versions (Web: x.x.x, API: x.x.x). Executor versions are shown separately in the Executors page. Keep all three in sync — running mismatched versions is not supported. A banner appears here when a newer version of Runner is available, with links to the Release Notes and update instructions.
License — paste your full license key here, including the -----BEGIN LICENSE----- and -----END LICENSE----- lines. Once a valid key is saved, this field shows the licensee name and expiry date instead. An Invalid License label appears if the key cannot be validated. Click Enter … to replace an existing key. Get a license key at nodepit.com.
Email
Email settings enable Runner to send notifications for run outcomes, user management events, and access token expiry. All outgoing emails use the sender details configured here.
Sender Name — the display name shown in the From field of outgoing emails, for example NodePit Runner. Optional — if left empty, only the sender email address is shown.
Sender Email Address — the From address for all emails sent by Runner.
SMTP URL — the connection string for your SMTP server. The format is smtp://user:password@host:port. Use smtps:// for a TLS connection. The field is masked by default; click Show to reveal it. Advanced options — such as disabling TLS certificate verification or setting a specific port — can be passed as query parameters following the Nodemailer SMTP URL format, for example smtps://user:password@host/?ignoreTLS=true.
Send Test Email — sends a test email to your own address to verify the configuration. The button is only available once the sender email address and SMTP URL are both filled in. Any delivery error is shown inline below the button.
Time Zone
Time Zone — the time zone used to evaluate all cron expressions. When a schedule is set to run at 0 9 * * 1-5, it fires at 9:00 am in this time zone. Click Use Current to set it to your browser's local time zone. All time zones from the IANA database are available, plus UTC.
WARNING
Changing the time zone affects all schedules immediately. Review your cron expressions after changing this setting to make sure runs still fire at the intended local times.
Cancellations
These settings define global timeout defaults for stuck runs. Both can be overridden per schedule in the Schedules settings.
Cancel Pending Runs After — if a run stays in the pending state longer than this threshold, Runner cancels it automatically. A run can get stuck in pending when no executor is available or when no executor matches the required tags. Options: never, 15 minutes, 1 hour, 6 hours, 1 day.
Cancel Running Runs After — if a run stays in the running state longer than this threshold, Runner cancels it automatically. Use this as a safety net for workflows that hang or exceed their expected duration. Options: never, 15 minutes, 1 hour, 6 hours, 1 day.