Agree, the only reason why I've added ```end``` is that it fires performance event with kind of important name ('startup-path-done') and shows 'no-data' view.

I'm not sure though what we should show to the user if such error occurred, before workaround it was just blank screen, with this temp workaround it will look like no message threads to display that I think is misleading. Probably we can show 'error' view with 'Try again', but in this case we need UX feedback.

Will file follow-up for that.