# Close existing allocation before changing cuts

**URL:** <https://forum.thegraph.com/t/close-existing-allocation-before-changing-cuts/121>\
**Category:** Questions & Feedback\
**Created:** [January 22, 2021, 3:11pm UTC](https://forum.thegraph.com/t/close-existing-allocation-before-changing-cuts/121 "2021-01-22T15:11:17Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![That3Percent](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/that3percent/32/62_2.png) [@That3Percent](https://forum.thegraph.com/u/That3Percent)\
**Post date:** [January 22, 2021, 4:32pm UTC](https://forum.thegraph.com/t/close-existing-allocation-before-changing-cuts/121/3 "2021-01-22T16:32:38Z")

</div>

I like the purpose behind this idea, but I don’t think it would work well exactly as stated for one reason:

An Indexer with no open allocations cannot serve queries. This would mean forcing an Indexer to shut down service to change delegation parameters - which is unacceptable for an Indexer providing critical services to dApps.

There might be better ways to achieve the same end. For example, I can imagine that the delegation parameters could be copied at the time the allocation was created. That way the Delegator has the same assurances that their potential rewards will not disappear.

---

_[View the full topic](https://forum.thegraph.com/t/close-existing-allocation-before-changing-cuts/121)._