"Run now with different settings” is disabled for Continuous Jobs even when the trigger is paused.

[javasquez]

Problem:
When a Databricks Job is configured with a Continuous trigger, the “Run now with different settings” option remains disabled even after the Continuous trigger is paused.

Limitation:
This prevents us from manually running the same job with different parameters for testing or ad-hoc executions. We can use “Run now”, but only with the job’s existing configuration.

It would be useful to enable “Run now with different settings” when the Continuous trigger is paused, allowing parameter overrides without modifying the job configuration.

[javasquez]

[data_pulse]

@javasquez 

I came across the same behaviour with a paused Continuous job that Run now was enabled but Run now with different settings remained disabled in the UI.

I tried triggering the same job through the Databricks SDK with overridden job parameter as:

from databricks.sdk import WorkspaceClient
w = WorkspaceClient()
w.jobs.run_now(
    job_id=<job_id>,
    job_parameters={"mode": "override"}
)

 The run started successfully and the parameter showed as override (resolved) in the job run.

So this looks like a UI limitation for Continuous jobs, while parameter overrides still work through the Jobs API/SDK.

[K_Anudeep]

Hello  @javasquez ,

This is an existing behaviour for Continuous jobs

“Run now with different settings” is not available for Continuous jobs, even when the trigger is paused. The Jobs UI disables that option whenever a job uses a Continuous trigger.

When a Continuous job is paused, you can still use Run now. That starts a run using the job’s saved settings. You cannot use the “different settings” flow to override parameters, select a subset of tasks, or change run-level settings.

What you can do

• Pause the Continuous trigger, then click Run now.
• To change parameters or other settings, update and save the job, then run it.
• After testing, unpause the trigger to resume Continuous execution.