Last Updated: 06 May 2020 14:23 by ADMIN
Created on: 02 May 2020 13:24
Category: Scheduler
Type: Bug Report
Bug in SchedulerDataSource: Creation of Recurring Weekly Event Has "Gaps" (Easy to reproduce)

Hi there, 


We are currently in the process of developing a booking/rota system utilising the latest build of the Kendo UI JQuery library and during internal testing we've spotted a bug in the creation of recurrence events within the scheduler control whereby "weekly" recurrences are created with numerous "gaps" in the scheduled events.   


To re-create this is quite simple,

1. Create a page containing a Kendo Scheduler control and configure pretty much with defaults (but allowing for the creation of weekly recurrent events).

2. Navigate to a specific month - the one we've been using to reproduce is June 2020.  (Don't think it matters which scheduler view you use).

3. Create a new event and set the recurrence rule to be:

  • Weekly
  • Every Mon, Tue, Wed, Thu, Fri
  • Start on 1st June 2020
  • End on 30th June 2020

4. Save the event.

You should see that most of the events are created, however for all but the first week in the recurrence the events that should be created on the Mondays and Tuesdays are missing.

I've done some digging around within the development console across a few different current browsers, and it looks to be a bug in the SchedulerDataSource "expand" method.   If you add an event with a recurrence rule specified as follows:


and then call the "expand" method on the data-source to split this into multiple events, you'll see that you actually end up with 14 events returned, rather than the correct 20.

This functionality is fairly critical to our current project, so would appreciate any feedback/response as soon as possible please.   Happy to provide further explanatory notes etc...if needed.


Many thanks






Posted on: 04 May 2020 11:49

Brilliant - thanks for the prompt response Ianko.  I'll pull down 2020.1.219 and revert our codebase to that version and re-test.



Posted on: 04 May 2020 11:05

Hello Jonny,

Thank you for the report. I converted this case to a bug report so that you can get updates on the progress. 

This is a regression bug and I have logged the bug with the highest priority and included it in the current sprint. We are very close to the code freeze of our release cycle and I cannot guarantee that we can include the bug fix in the upcoming release. 

Currently, my only possible suggestion for a workaround is using the 2020.1.219 version instead.

Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.