# \`queryParams\`, \`setupController\`, \`refresh\`, oh my!

**URL:** <https://discuss.emberjs.com/t/queryparams-setupcontroller-refresh-oh-my/7195>\
**Category:** Ember Data\
**Created:** [January 30, 2015, 2:55pm UTC](https://discuss.emberjs.com/t/queryparams-setupcontroller-refresh-oh-my/7195 "2015-01-30T14:55:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![artsyca](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/artsyca/32/9693_2.png) [@artsyca](https://discuss.emberjs.com/u/artsyca)\
**Post date:** [January 30, 2015, 2:55pm UTC](https://discuss.emberjs.com/t/queryparams-setupcontroller-refresh-oh-my/7195/1 "2015-01-30T14:55:01Z")

</div>

In brief: we’re using queryParams on our route and controller to automatically 'refresh()`.

In setupController, setting any of the target properties will trigger refresh and cause data to load multiple times.

Currently we’re implementing a flag to toggle `isRefreshEnabled` with a check inside the `refresh` function but it seems like we’re just patching an underlying Ember issue?

I’d be very interested to know if anyone has run into this issue and what can be done about it?