Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ISSUE] databricks.sdk.service.jobs.run_now_and_wait() NotFound #922

Open
aureliodove opened this issue Mar 7, 2025 · 0 comments
Open

Comments

@aureliodove
Copy link

Description
I have been running jobs.run_now_and_wait(job_id=job_id, timeout=timeout) for a while now with no issues. Today when I ran it I got this error: NotFound: Bad Target: /api/2.2/jobs/run-now.

Reproduction
from databricks.sdk import WorkspaceClient
from databricks.sdk.service import jobs
import datetime

w = WorkspaceClient()
timeout = datetime.timedelta(hours=20)

Get job_id from existing job

run_by_id = w.jobs.run_now_and_wait(job_id=job_id, timeout=timeout)

Expected behavior
The expected behavior is it will kick off the job it calls and when that job completes successfully the parent job will also complete successfully.

Is it a regression?
This worked last week with version 0.44.1.

Debug Logs
The SDK logs helpful debugging information when debug logging is enabled. Set the log level to debug by adding logging.basicConfig(level=logging.DEBUG) to your program, and include the logs here.

Other Information

  • OS: [e.g. macOS]
  • Version: [e.g. 0.1.0]

Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant