Why can't I delete a Run Workload?

Run allows deletion of an unused Workload. A Workload with deployment history is retained, and the delete request returns Workload has deployment history and cannot be deleted. Cancelling an attempt does not remove its deployment history.

Confirm which Workload you are removing

Use the Socra CLI with the Account and Run plugins, signed in to the Account that owns the Project. Replace WORKLOAD_ID with the Workload's wrk_… ID:

socra run workload get WORKLOAD_ID

Check its name and Project before taking any action. Then replace PROJECT_ID with that Project's ID and inspect its deployments:

socra run deployment list --project PROJECT_ID

Match the deployment records to the Workload ID. Continue with --after when the list has more pages; the first page does not prove that the Workload has no history.

Delete an unused Workload

If the Workload has never been deployed and you intend to remove its configuration, use:

socra run workload delete WORKLOAD_ID

The command removes the unused Workload. Retrieve the same ID again to verify the result. If the server rejects deletion because history exists, repeated requests will not clear that history.

Separate removal from stopping an attempt

A Deployment can be cancelled while it is in progress. Cancellation concerns that attempt; the Workload and its history remain. Inspect the Deployment's resulting state to confirm what happened.

Deleting a Project has a wider scope than deleting one Workload. Do not delete a Project solely to bypass this Workload error. Disabling a service or changing a Project's status also does not establish that every resource was removed or every charge has settled.

Before retiring an application, identify its active resources and service-specific removal requirements. Keep the relevant Workload and Deployment IDs so you can account for retained history. The Run reference lists the supported lifecycle operations.