seems like due to a delay.
When opening a page with a listening dataview to a listvie, the first object of the listview will be selected and displayed in the dataview. This will trigger the nanoflow to retrieve the list for the listview.
My guestimation is that when selecting another object in the first listview, the refresh and (re)trigger of the nanoflow doesn't execute as it should. I would file a bug report
Next to that; why do you need custom logic to retrieve a list? I try to avoid datsource micro/nanoflows as much as possible. if the retrieve/dependencies of the list is to complex, a microflow would be better, you need to connect with the database in any case, thus clientside logic is not what you need.