We successfully reproduced this at our side and we can confirm it is a bug at our side. It happens if the time for the service call is almost the same as the DisplayAfter time. I have logged it into our PITS so you can track its status here
. We will try to fix this for the next official release.
the Telerik team
Sharpen your .NET Ninja skills
! Attend Q1 webinar week and get a chance to win a license! Book your seat now >>