CODEWITHSUNDEEP
google-apigoogle-calendar-apigoogle-api-dotnet-client
PNC
PNC

Reputation: 1972

Google Calendar v3 Error "The requested minimum modification time lies too far in the past. [410]"

We are using the Google Calendar v3 API to return a list of events for a user that have been updated since a point in time.

In the v2 API there was no limitation on setting this date in the past.

If we set the UpdatedMin to a date too far back (like 2 months) then the error is thrown

"The requested minimum modification time lies too far in the past. [410]"

If we set ShowDeleted to false then we do not get the error.

I cannot find any reference to a limitation here. Does anybody know the details of this limit. Unfortunately when synchronising calendars this is a show stopper when synchronisation has not run for a period of time for a calendar (other than running a full list which we would prefer to avoid)

EventsResource.ListRequest lr = new EventsResource.ListRequest(service, c.uc.calendar); 

lr.UpdatedMin = c.primaryModTime.ToLocalTime();
lr.ShowDeleted = true;
Events el = lr.Execute();
if (el.Items.Count > 0)
{

the following also discusses this issue but without any resoluton.

https://groups.google.com/forum/#!msg/google-calendar-api/_rk9o45sXT0/3APXqxi8jvkJ

Upvotes: 1

Views: 3575

Answers (1)

luc
luc

Reputation: 3782

There is some explanation at:

https://developers.google.com/google-apps/calendar/v3/sync

It says that on 410 you should wipe your storage and perform a full sync instead.

Also consider switching to sync tokens as recommended in the last paragraph.

Upvotes: 4

Related Questions