Temporary Change to Job Parallelism Defaults – Azure North Europe
Starting Tuesday, March 10, 2026 at ~12:00 UTC, we will run a temporary platform evaluation on the Azure North Europe stack related to job parallelism behavior. This change is part of ongoing work to modernize internal platform capabilities and align scheduling behavior across stacks.
What is changing?
For jobs that contain components with configuration rows, projects that currently have parallelism disabled (parallelism = 0) or do not have a parallelism setting configured will temporarily run with default parallelism = 1.
Both settings result in sequential execution, but parallelism = 1 follows the standard scheduling behavior used across the platform, while parallelism = 0 represents a legacy configuration mode.
Possible impact
Because this is an evaluation period, the impact may vary between projects depending on their workloads.
Possible effects may include differences in total job runtime.
Timeline
- Start: Tuesday, March 10, 2026 ~12:00 UTC
- Evaluation period: ~5 days
- End: Friday, March 14, 2026 ~12:00 UTC
Who is affected?
This change affects projects on the Azure North Europe stack that:
- have parallelism set to 0, or
- do not have a parallelism setting configured
and run jobs that include components with configuration rows.
Contracted customers are excluded from this evaluation.
What do you need to do?
No action is required. If your jobs on components with configuration rows are running slower, increase their parallelism.
If you notice unexpected behavior in job execution during this period, please contact Keboola Support.