Maybe I'm making this up, but it's my impression that the higher the startIndex parameter, the more likely it is for the API query to time out.
If in fact I have no way to filter my Contents using creationDate or published, then in order to have an ongoing download of contents, I need to sort by creationDateAsc and get the most recent (i.e. highest) pages of results. I can't do creationDateDesc because I can't know (or at least it's much harder to know) where my existing data is going to begin.
We're up to 134,000 content items -- which means lots of timeouts. Very frustrating!
Really hope to get the filter working here. If I'm right about the timeouts, this would mean a better result for me and less of a load on Jive's servers.
Hi Spoorthy, I mentioned sorting by dateCreatedDesc in my reply above (though I typed it wrong). As I wrote before,
<<I can't do dateCreatedDesc because I can't know (or at least it's much harder to know) where my existing data is going to begin.>>
I see this question is still open. Not sure if this issue still matters to you but posting here for the sake of other developers.
I see your dates are not arranged in the way API needs it. Swap both dates and see the magic. See below details.
Wrong filter: ?filter=creationDate(2015-04-28T15:16:55Z,2015-04-28T12:16:55Z)
Correct filter: ?filter=creationDate(2015-04-28T12:16:55Z,2015-04-28T15:16:55Z)
Template is: ?filter=creationDate(<From>,<To>)
Hope this helps.