You know I figured what was triggering the problem, but still did not delve into why it is happening though. The error in my previous (old version) and current code is triggered by the scheduler I used. These two schedulers causes the problem: Schedulers.Randomly and Schedulers.ByID, however, in the latter we can achieve the same behavior by using Schedulers.ByProperty(:id). 