Weird workflow error - Error in run but job does not exist
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
Hello,
I have an error:
Job | link (116642657143475) |
Job run |
|
Task run | link (74750905368136) |
Status |
Failed |
Started at | 2025-01-14 07:48:16 UTC |
Duration | 2m 40s |
Launched | Manually |
If I try to access this job I get :
The job you are looking for may have been moved or deleted.
Which is correct, I have deleted that job and created a new one that is scheduled. But somehow this job gets triggered anyway and manually. I have tried getting info but in UI and through API but since job does not exist I cannot remove it .
I deploy workflows through AZDO Devops and maybe there is a glitch between branches or something.
Anyone seen this before?
Many thanks!
- Labels:
-
Workflows
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
Redeploy the workflow and verify that the job configuration is up to date
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
The job has been deployed and is running fine. However this old configuration keeps running and failing. This job is in some kind of limbo. The job id does not exist but somehow gets triggered "manually".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
how you deleted the problematic job?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
In all the runs you see that it fails it always shows the same job id, isnt it possible that this can be triggered as a single job run via API?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
@saurabh18cs I deleted the job by creating a new notebook and task. Everything is done through AZDO and I suspect that there is a glitch between the branches.
@Walter_C The job id only exists as a failure. The job id is always the same but does not exist in workflows in the UI or if you query the API.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
if you open another job and in the URL change the job id to this one, it also does not show anything?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
Nope same, job not found.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
This is weird issue, do you have access to submit a support ticket so we can look further on it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
I will try to sync branches and re-deploy . Even weirder if I try to delete with API
I get:
Failed to delete job. Status code: 403, Response: {"error_code":"PERMISSION_DENIED","message":"User does not have Owner or Admin permissions on job 116642657143475"}
But I cannot find job with that ID with /api/2.0/jobs/list
😀😀
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
- Review your automation scripts (e.g., Terraform, CI/CD pipelines) to ensure that they are not referencing the deleted job.
- Update the scripts to remove any references to the deleted job.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
will do . Thanks