I don't think it's a serious bug, just a user-experience issue. It works as intended, whereas we never intended folks to include multiple queries against events-based tables in their schedule.