Google Calendar API“请求的最短修改时间过去太久了."仅仅一天之后 [英] Google Calendar API "The requested minimum modification time lies too far in the past." after just one day

查看:61
本文介绍了Google Calendar API“请求的最短修改时间过去太久了."仅仅一天之后的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的代码使用具有以下参数的 service.events().list()获取日历事件:

My code fetches calendar events using service.events().list() with the following parameters:

timeMax: 2015-11-13T04:12:44.263000Z
timeMin: 2014-05-17T04:12:44.263000Z
updatedMin: 2014-11-12T14:56:20.395000Z # = yesterday

我知道 updatedMin 参数有一个限制,可以防止它过去太远,但是最近,即使 updatedMin 昨天:

I know there's a limit on the updatedMin param that prevents it to be too far in the past, but lately I get the following error even when updatedMin is yesterday:

要求的最短修改时间过去太久了.

The requested minimum modification time lies too far in the past.

无处不在 错误,他们谈论的是大约一个极限.过去20天,当然不是一天.

Everywhere this error is mentioned, they are talking about a limit that is approx. 20 days in the past, certainly not one day.

有什么主意导致此错误吗?

Any ideas what is causing this error?

推荐答案

@Tzach,我在

@Tzach, I tried the above query in API explorer with the same values and it returned the results without any error unless its greater than 20days. As Luc said, better to switch to syncTokens which saves the bandwidth.

这篇关于Google Calendar API“请求的最短修改时间过去太久了."仅仅一天之后的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆