An Azure machine learning service for building and deploying models.
Deleted Azure ML job stuck showing "Running" in Jobs list for a month
In Azure Machine Learning Studio, a job in workspace still appears in the Jobs list with status "Running", even though it was deleted about a month ago. Opening the job returns "The job doesn't exist or has been deleted."
The record is confirmed gone on every API surface — v1 Run , v2 jobs.get , and jobs.archive all return 404 "not found" — yet the Jobs list keeps rendering the row. So cancel/archive/delete/refresh have nothing to act on; it looks like an orphaned run-history list-index entry.
Question: How can this orphaned "Running" row be removed from the Jobs list, given the underlying run no longer exists?