Occasionally, a Job run in the Transient Workspace could leave content that cannot be removed in the user interface. In this circumstance, a customer could open a Jira ticket to request deletion of the content. Prior to a request for content deletion, a customer should undertake the following steps:

1. Clean up all broken or hung SAS^® sessions from the SAS^® Sessions panel in the user interface
2. Request a listing of all remaining .transient workspaces.
3. For folders associated with Jobs, access the Published History of the Job and locate its corresponding failed Job entry.  To see objects associated with the failed Job, select its associated manifest (user must be the owner of the transient workspace to view it).  Select retry check-in if the Job objects are desired.  Note, this action overwrites objects from more recent runs if they exist.
4. As a last resort, the customer can request SAS^® to delete the remaining .transient workspaces from the operating system. 

At the completion of these steps, they can request to delete content from the .transient workspace that has a time stamp older than the entries in the SAS^® sessions tab. 

A couple of examples are:

1. Before any steps above are followed, if the oldest SAS session has a date of 1/1/2018, then the customer can request to have all empty folders with time stamp prior to 1/1/2018 deleted.
2. If a customer has completed the steps above but still has folders (with or without files in them) with timestamps prior to the oldest SAS session of 2/1/2018,  they can request to delete the files and folders with time stamps prior to 2/1/2018 to recover .transient space.

Operating System and Release Information