Apex Code Development You need to sign in to do that
Don't have an account?
Kiti API: getUpdated call not returning up to date results
Hi,
Salesforce's getUpdated request returns a list of record ids that have
been updated in a given time window. It also returns
'latestDateCovered' which confirms to the requestor the time window in
which these records were updated.
We send a request as follows:
getUpdated(sObjectType startDate EndDate)
After each request we store the latestDateCovered to use as the
startDate for the next request, and we always set the EndDate to be now.
We make this request every 10 minutes and usually everything is fine.
However yesterday we noticed that the request seemed to get "stuck":
i) We made a request at 11:02 UTC and the value for latestDateCovered
was 2008-07-21T10:57:00.
ii) We made our next call at 11.12 UTC and the value for
latestDateCovered was still 2008-07-21T10:57:00.
iii) Repeated ii over and over until...
iv) ...about 18:15 UTC when the latestDateCovered
suddenly jumped to 2008-07-21T18:12:00.
This means that towards the end of yesterday the API wasn't reporting
changes for over 7 hours and our systems were very out of sync.
So my questions are:
1) Has anyone else seen this happen before and what did you do?
2) Does anyone know what Salesforce consider an acceptable delay for
these sort of API calls to be? I can't find anything about this on the
API Developer's Guide at all. This is a business critical function for
us, and a 20 minute delay would be fine, but several hours was a serious
problem.
We first experienced this problem on two consecutive days a month ago
but unfortunately our support ticket is still pending.
Thanks for any help.
Katherine
Salesforce's getUpdated request returns a list of record ids that have
been updated in a given time window. It also returns
'latestDateCovered' which confirms to the requestor the time window in
which these records were updated.
We send a request as follows:
getUpdated(sObjectType startDate EndDate)
After each request we store the latestDateCovered to use as the
startDate for the next request, and we always set the EndDate to be now.
We make this request every 10 minutes and usually everything is fine.
However yesterday we noticed that the request seemed to get "stuck":
i) We made a request at 11:02 UTC and the value for latestDateCovered
was 2008-07-21T10:57:00.
ii) We made our next call at 11.12 UTC and the value for
latestDateCovered was still 2008-07-21T10:57:00.
iii) Repeated ii over and over until...
iv) ...about 18:15 UTC when the latestDateCovered
suddenly jumped to 2008-07-21T18:12:00.
This means that towards the end of yesterday the API wasn't reporting
changes for over 7 hours and our systems were very out of sync.
So my questions are:
1) Has anyone else seen this happen before and what did you do?
2) Does anyone know what Salesforce consider an acceptable delay for
these sort of API calls to be? I can't find anything about this on the
API Developer's Guide at all. This is a business critical function for
us, and a 20 minute delay would be fine, but several hours was a serious
problem.
We first experienced this problem on two consecutive days a month ago
but unfortunately our support ticket is still pending.
Thanks for any help.
Katherine
I think you misunderstand what the lastDateCovered means, it does not mean that there are no changes for after that date, it just means there are potentially some changes being processed from that date. You are getting all the committed changes as of the time of your request, even if lastDateCovered is for a time 4 hours ago.