In your attached image, the compute environment is clearly labeled "Serverless," which confirms that the job is not using a dedicated or job cluster as intended
Use the GET /api/2.0/clusters/get endpoint with your cluster_id to retrieve cluster details.
Inspect the "state" field in the response JSON, which indicates the cluster status such as "RUNNING", "TERMINATED", "PENDING", etc.
If the cluster state is anything other than "RUNNING", it implies the cluster is either stopped or provisioning, which might cause a fallback to serverless compute for jobs.
If you see discrepancies in the system.billing.usage table (like serverless compute being used), that further suggests that the job isn't properly associated with the cluster
Set the Cluster as the Only Compute Option
If the issue persists, ensure no other conflicting compute resources are configured. For example, if you are using multiple compute options, double-check that only the cluster you intend to use is included and confirm in logs
