Non-existent filter value turns Flexmonster to infinite loop

Hi all,
I'm using Flexmonster with Flexmonster accelerator connected to SSAS cube. Both in version 2.315. We have some saved reports which can be executed against few different cube instances with different data.
Now, when I define e.g. page with filter

"pages": [
 {
   "uniqueName": "[BusinessPeriod]",
   "levelName": "[BusinessPeriod].[Year]",
   "caption": "Year",
   "sort": "unsorted",
   "filter": {
      "negation": false,
      "members": [
        "[BusinessPeriod].[All].[2009]"
      ]
   }
 }
]

I'm not able to open the report on cubes which does not contain any data for filtered value, in this case 2009. Flexmonster is stuck, it shows that it is loading members for Year dimension - http://imgur.com/a/pestS
When I open the network monitor in the browser, I can see that Flexmonster is querying the server in an infinite loop. The requests look like:

"method": "POST",
 "url": "http://172.17.16.81:50005/FlexmonsterProxy/DiscoverMembers",
 "httpVersion": "HTTP/1.1",
 "headers": [
 ...
 ],
 "queryString": [],
 "cookies": [],
 "headersSize": 511,
 "bodySize": 524,
 "postData": {
 "mimeType": "application/json; charset=UTF-8",
 "text": "{\"catalog\":\"VistaBI\",\"cubeUniqueName\":\"Box Office Summary\",\"subquery\":\"\",\"hierarchyUniqueName\":\"[BusinessPeriod]\",\"properties\":\"\",\"memberUniqueName\":\"\",\"allMemberName\":\"[BusinessPeriod].[All]\",\"hasAllMember\":true,\"loadAll\":false,\"searchPhrase\":\"\",\"chunkIndex\":595,\"ascendants\":\"[BusinessPeriod].[All].[2009]\",\"siblings\":\"\",\"activeLevel\":\"[BusinessPeriod].[Year]\",\"credentials\":null,\"sessionId\":63629324975240,\"customData\":\"\",\"localeIdentifier\":\"\",\"effectiveUserName\":\"\",\"roles\":\"\",\"signature\":\"BR1tPcsn0Y0mGgqPLk2J/JTrdns=\"}"
 }

And the response is always the same:

{"error":null,"data":{"all":0,"count":0,"members":[]}}

I believe this is wrong behavior and it prevents us to start using Flexmonster. I would expect that the filter is ignored if the value does not exist anymore. Or at least to have option in configuration where you can set this behavior. BTW, this is probably happening on all filters, not just page filters - at least on column filters it is the same.

UPDATE: I found out that it happens probably only for levels of hierarchies that do have any child levels - e.g Year. When you have a filter for non-existent value on the leaf level - e.g. Day - it works as expected: filter is ignored

Regards
Lukas Navratil