You may have other causes holding this data in place (Dedupe files still in use, Managed Disk Space, etc). I would see if Managed Disk Space is in use and if so, disable it, then rerun Data Aging to see if that releases the space. If you are using Deduplication, it may be reporting the expected space assuming the jobs are of the non-deduped size as well.
If you are out of space, Iw ould suggest focusing on the jobs themselves. See what has a prune date in the past and find the reason the job has not pruned yet.