Here are a few RRULES that throw an HTTP 500 on creation: DTSTART;VALUE=DATE:20020331 DTEND;VALUE=DATE:20020401 RRULE:FREQ=YEARLY;INTERVAL=1;BYMONTH=4;WKST=SU
DTSTART;TZID=Europe/Amsterdam:20090104T110000 DTEND;TZID=Europe/Amsterdam:20090104T140000 RRULE:FREQ=WEEKLY;UNTIL=20090103T225959Z;INTERVAL=1;BYDAY=SU DTSTART;TZID=America/Los_Angeles:20010107T080000 DTEND;TZID=America/Los_Angeles:20010107T080000 RRULE:FREQ=MONTHLY;UNTIL=20100101T160000Z;INTERVAL=12;BYDAY=1SU;BYMONTHDAY=7 DTSTART;TZID=Europe/Amsterdam:20090104T110000 DTEND;TZID=Europe/Amsterdam:20090104T140000 RRULE:FREQ=WEEKLY;UNTIL=20090103T225959Z;INTERVAL=1;BYDAY=SU DTSTART;TZID=America/New_York:20090518T130000 DTEND;TZID=America/New_York:20090518T133000 RRULE:FREQ=WEEKLY;UNTIL=20090518T035959Z;INTERVAL=1 DTSTART;TZID=Europe/London:20080909T190000 DTEND;TZID=Europe/London:20080909T230000 RRULE:FREQ=WEEKLY;UNTIL=20080909T175959Z;INTERVAL=1;BYDAY=TU;WKST=SU DTSTART;TZID=America/Los_Angeles:20090302T080000 DTEND;TZID=America/Los_Angeles:20090302T083000 RRULE:FREQ=WEEKLY;UNTIL=19691231T160000Z;INTERVAL=1;BYDAY=MO Yes, they're all somewhat problematic, but they all came out of real people's calendars. Until recently these didn't cause a problem. Please don't tell me I'm going to have to pull apart the RRULES I'm given, validate and fix them, and then send them to Google. -c On Sep 2, 6:06 am, Charlie Wood <[email protected]> wrote: > Thanks. Yes, it looks like they're all recurrence-related. > > Can anyone from Google provide some guidance as to what changed? > > Thanks, > Charlie > > On Sep 2, 3:59 am, getaceres <[email protected]> wrote: > > > > > They have changed something. I had some code that worked in July and > > suddenly it started failing with error 500 on August. It was a problem > > with the recurrence. In the UNTIL field I was sending a date with time > > and I had to send only the date. Also other people are having problems > > with the recurrence. I think that they changed the ical parser. > > > On Sep 1, 11:48 pm, Charlie Wood <[email protected]> wrote: > > > > We're seeing tons of HTTP 500 errors coming from Calendar API calls > > > that have been operating without any errors for a long time. They're > > > for both creation and update of various events. Sometimes the body of > > > error us "Exception during update", other times "Internal error". > > > > We're contacting some of the affected users (there are hundreds) to > > > see if they can access Google Calendar via the web. In the mean time, > > > is this something Google is aware of? > > > > Any updates would be appreciated. > > > > Thanks, > > > Charlie > > > Spanning Sync --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
