GET trends/place stalled


#1

The GET trends/place API call are returning the same set of trends at least for Spain (23424950) & Venezuela (23424982) since 2015-06-12 22:42:30.

Please someone can check the servers attending the apps connecting from US IP addresses?

Thanks,


#2

@andypiper could you take a look at this, please?


#3

Are you still seeing this? I can’t seem to reproduce. The timestamps look fresh, and the trends for Spain are updating between invocations AFAICT.


#4

@andypiper, thanks for your answer.

Unfortunately, is returning the same set of trends on every API call, but now only for Spain.

As you can see on the following link, the API call stalled for several days/hours at least 5 times since 2013:

Our server is located at Orem, UT 84097.


#5

@andypiper an update: World Wide (1), Argentina (23424747), Kenya (23424863), Poland (23424923), Malaysia (23424901) and New Zealand (23424916) are also answering with the same set of trends.


#6

You mean, all of them show an identical set of trends across all of the WOEIDs? or that each one of them continues to show the same trends on multiple invocations over (say) an hour long period? I see you’ve reported this before but unfortunately I can’t be sure which behaviour you’re describing based on those reports.

I’m sorry for the repeated frustration you’re encountering here!


#7

@andypiper no, for each WOEID mentioned, each set of 10 trends has been repeated since Friday (each one of them continues to show the same trends on multiple invocations since friday).

I remember something, in one of the previous occasions, about the need to flush the trends cache in some regional servers.

Thanks for your interest.


#8

OK great - thanks for clarifying - I’ll see what we can do on this.


#9

Thank you. I really appreciate.


#10

Update: For 2 hours, between (created_at) 2015-06-15 22:08:15 and 2015-06-15 23:58:11 the API call responded with fresh set of trends for the mentioned WOEIDs.

At 2015-06-16 00:05:33, the system began to respond with the same previous 10 trends: 2015-06-15 22:00:17 :frowning:


#11

@andypiper Update: From 2015-06-16 04:12:47 to 2015-06-16 04:43:10 the API call responded with fresh set of trends for the mentioned WOEIDs.

At 2015-06-16 04:49:10, the system began to respond with the same old set of trends.


#12

@andypiper Update: No update at all.

I’m sorry for bother you. I am worried because we are not reporting new trends for the selected countries since last friday.


#13

@andypiper Update: From 2015-06-16 17:00:42 to 2015-06-16 18:50:54 the API call responded with fresh set of trends for the mentioned WOEIDs.

Unfortunately, since 5 minutes ago (2015-06-16 18:52:43) we get the same set of trends on every API call.


#14

@andypiper good news: Since 2015-06-16 21:10:48 everything has been working perfectly. Thank you very much for your support and sorry for the inconvenience.