Use Cases
Overriding environment variables at the schedule level is useful for:- Environment-specific configurations - Different values for development, staging, and production schedules
- Schedule-specific parameters - Custom thresholds, limits, or settings per schedule
- Testing and debugging - Temporary value changes without affecting global settings
- Multi-tenant deployments - Client-specific configurations within the same workspace
Configuration
To override environment variables for a Bolt Schedule, follow these steps:- Navigate to the Bolt UI and select the schedule you wish to edit.
- Click “Edit” in the top right corner.
- Scroll to the Environment Variables Override section.
- In the Override column, enter a new variable value. If empty, Paradime will use the inherited value set at the workspace level.
- Click “Deploy” to save your changes.

How Overrides Work
- Precedence: Schedule-level overrides take precedence over global environment variable values
- Scope: Overrides only affect the specific schedule where they are configured
- Inheritance: If no override is set, the schedule uses the global variable value
- Validation: The system validates that the variable exists globally before allowing an override