orphan queries in running state

meanwhilefurthe
New Contributor III

We have a job submitted through the Spark Connect API, and running on Serverless Compute.

The job got canceled twice and left a total of 14 queries orphan, they are in a weird state because the running time is not increasing, but they are there showing up as running.

There is no UI for serverless compute, the spark ui is not available either given that the compute is managed by databricks too, the api for cancelling the queries returns an empty response which apparently is supposed to, but the queries are still there in a running state.

Any way to cancel these queries? There is no cancel button in the UI either..