I see some Join Two Datasets jobs. Those can often create really large results (all versus all match!) but it doesn’t look like your data / data size / query would NOT do this, so ignore. I’ve posted the info here for others that might run into this kind of problem in the future (it happens).
I do also see many many now purged unnamed histories. These might have been created by a workflow (if the inputs are multiple single datasets and the output is “send to a new history”). How a problem like that looks and how to avoid it is in this prior post – in short, use dataset collections or just accept that is how the functionality works when not using collections + using output to new history: Workflow Splitting Samples Automatically
If these last two posts doesn’t cover what you think went wrong, please explain more about what you were doing & share links as appropriate.
Thanks! Jen