My bad, I actually made a code that caused our logging to print out the unix time when I would start polling again instead of the seconds to back off for like it previously had.
Mea Culpa! Ben On Oct 29, 2:23 pm, Chad Etzel <c...@twitter.com> wrote: > Hi Ben, > > It sounds like that value is a unix timestamp, which is a bug. The > retry-value should be a "seconds from now" value... The search team is > investigating. Thanks for reporting. > -Chad > > > > On Thu, Oct 29, 2009 at 2:00 PM, Benjamin Darfler <b...@bdarfler.com> wrote: > > > We are using the search api and respecting the 503 and retry-after > > values however I've seen a retry value in the 40 YEARS range a few > > times in the past week. Whats up with that? > > > Ben