# Quota reset issues

**URL:** <https://help.galaxyproject.org/t/quota-reset-issues/1371>\
**Category:** Uncategorized\
**Tags:** storage-dashboard\
**Created:** [May 23, 2019, 2:25pm UTC](https://help.galaxyproject.org/t/quota-reset-issues/1371 "2019-05-23T14:25:28Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\
**Post date:** [May 24, 2019, 12:47am UTC](https://help.galaxyproject.org/t/quota-reset-issues/1371/6 "2019-05-24T00:47:25Z")

</div>

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](https://help.galaxyproject.org/t/workflow-splitting-samples-automatically/1344/)

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

---

_[View the full topic](https://help.galaxyproject.org/t/quota-reset-issues/1371)._