# CASE: limit range below 200 accounts (error "Range 'some range' would have more than 200 items") **URL:** \ **Category:** Cases\ **Tags:** range, error\ **Created:** [August 18, 2020, 6:43am UTC](https://community.silverfin.com/t/case-limit-range-below-200-accounts-error-range-some-range-would-have-more-than-200-items/1900 "2020-08-18T06:43:25Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![sven](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.silverfin.com/sven/32/1495_2.png) [@sven](https://community.silverfin.com/u/sven)\ **Post date:** [August 18, 2020, 6:43am UTC](https://community.silverfin.com/t/case-limit-range-below-200-accounts-error-range-some-range-would-have-more-than-200-items/1900/1 "2020-08-18T06:43:26Z")
In rare cases, you might accidentally bump into an error that mentions the following: > Liquid error: Range ‘140100\_\_140350’ would have more than 200 items, which is not allowed in code: assign some\_accounts = period.accounts | range:some\_range **What does this error mean?** This error means that the variable that defines the range (so `some_range`) has more than 200 possible accounts to be checked. We don’t allow this, due to performance reasons. So giving a range like `1__7` means in the background, 7 items are checked by the background query (meaning, less than 200), which will be fine. However, a range like `700100__700301` will mean the background query will check 201 possible ranges (more than 200), and will result in an error. **How can this be solved?** In the rare cases you do need to call upon all these accounts, you’ll need to split up the range in several parts, like this: ```auto {% comment %}define several ranges where each part does not have more than 200 accounts{% endcomment %} {% assign some_range = "14010_14034,140350" %} ``` So by splitting the range into several parts, where each part does not have more than 200 items, can you workaround this error. We hope this happens rarely though, but figured it probably is worth mentioning it.