Yes, I can reproduce the issue. Unfortunately, I do not have an immediate solution, only a clue that it is somehow connected with destroying the scheduler and then re-creating it again. I'll check the destroy process tomorrow.
Although create-destroy-create should work flawlessly, there is another approach demonstrated in our advanced
example which uses reuse routing strategy. You can take a look at it meanwhile.