Environment Variable Overrides

Environment variable overrides let a schedule use different values without changing your workspace configuration. A schedule resolves each variable through a cascade, so you set a value once at the broadest level and override it only where you need to.

​

How a value is resolved

For each variable, Bolt takes the most specific value available, in this order:

1. Schedule override — the value you set on this specific schedule. If present, it always wins.
2. Environment value — the value set for the environment this schedule runs in (for example, production).
3. Workspace default — the base value configured in workspace settings.

In other words, a schedule inherits the workspace default, an environment-specific value can override that default, and a schedule-level override ultimately wins for that job. If you leave the schedule override empty, the schedule falls back to the environment value, and then to the workspace default.

​

When to override

• Environment-specific configuration — different values for development, staging, and production schedules.
• Schedule-specific parameters — custom thresholds, limits, or settings for one schedule.
• Testing and debugging — temporary value changes without touching the workspace default.
• Multi-tenant deployments — client-specific configuration within the same workspace.

​

Set an override

1. In the Bolt UI, open the schedule you want to edit.
2. Go to the Environment variable overrides section.
3. In the Override column, enter a new value for the variable. Leave it empty to keep the inherited value (the environment value, or the workspace default).
4. Click Deploy to save.

Overrides only affect the schedule where they are set. The workspace default and other schedules are unchanged.