Hi, I've noticed that DCS (1.2) will not return an event instance more than 356 days from the creation of the event in a calendar-query. It seems to be related to Trac ticket #207 (except that it affects non-recurring events too) I've found that these events are not put into the TIMESPAN index, which means that they are not returned by a search using the index. Searches seems to not use the index when there's a time-range element in the filter, but the exception detecting this is only thrown from the filter expression generator for prop-filters, ... which again means that if you don't have a prop-filter in your query, you'll get a search using the index, which will ignore these 356+ days events. On the other hand... if you have a prop-filter or patch the DCS source to throw ValueError exceptions every time there's a time-range, all your calendar-queries will do a brute force search on all resources. ... in which case it might be faster for a client to just GET the calendar resource it self. Is this correctly observed? If so, is this behavior excepted? kind regards, Peter Mogensen