Not receiving tweets anymore over streaming API

zorrobiwan · 2014-05-16T16:27:46.000Z

Thx a lot !

romainhuet · 2014-05-16T16:32:27.000Z

You’re welcome. Let us know how things work on your side, Pascal! Thanks.

stockpulse4 · 2014-05-16T16:50:08.000Z

Seems to be working again on our side. Thank you for the fix. We will further observe it and let you know once we find something.
best, Stefan

mgosmant · 2014-05-16T19:00:16.000Z

yep, it works. Thx

romainhuet · 2014-05-16T21:38:32.000Z

Thank you for the note, Stefan. Glad to hear it is working again on your side.

romainhuet · 2014-05-16T21:38:44.000Z

Perfect, glad to hear. Thanks Maxime!

mgosmant · 2014-05-21T04:47:42.000Z

Is it possible this is happening again with user tracks ? It seems our user tracking is getting very low volumes since last 6 hours.

zorrobiwan · 2014-05-21T04:50:09.000Z

Same observation here. It’s happening again (delay and some Tweets are not coming)

romainhuet · 2014-05-21T09:43:53.000Z

Maxime, Pascal,

Thanks for the report. Just to be clear, is the issue you are encountering with the follow parameter to receive Tweets from a selection of users? Is everything working as expected with track for keywords?

Thanks,
Romain

zorrobiwan · 2014-05-21T09:49:52.000Z

On my side, one of my client report me problem to collect Tweets based on keywords (so track)

Thx for your help

romainhuet · 2014-05-21T10:54:26.000Z

Thanks, I reported to the engineering team and I am performing some tests on my end. I will reply to this thread as soon as possible with updates on the matter.

romainhuet · 2014-05-21T14:39:27.000Z

Maxime, Pascal,

I am currently investigating with the engineering team. If you have any specific use cases that could help make sure we fix your issues, such as sample Tweets that should have been streamed given your parameters but were not, that would be much appreciated.

Thanks,
Romain

zorrobiwan · 2014-05-22T07:46:00.000Z

Unfortunately I’m not be able to find a interesting test case.
Once I get one, I’ll inform you

Thx

romainhuet · 2014-05-23T12:58:54.000Z

Hello,

Just checking in here. Are you still encountering any issues with the Streaming APIs?

Thanks,
Romain

stockpulse4 · 2014-05-23T13:10:20.000Z

Hi Romain,
we don’t have any issues on our side. We are using track and follow, both are working fine.
thanks, Stefan

HeapsOfStacks · 2014-05-23T20:10:29.000Z

Still having trouble with the stream on my end. Using only follow and no track keywords.

scottnicolson · 2015-04-01T16:11:09.232Z

Hi Romain,

What is the status of this issue? Last year we ran a few campaigns where case sensitivity of the tracked hash tag didn’t seem to matter. However in my latest tests the hash tag is case sensitive… most of the time.

The documentation still says that the track values are case insensitive.

Any update would be most helpful.

Cheers
Scott

umersafeer · 2016-05-10T18:06:38.820Z

geting that error when accessing tweets using apache flume it is working fine for me couple of days ago …
plz help

2016-05-10 19:38:09,638 (Twitter Stream consumer-1[Establishing
connection]) [DEBUG -
twitter4j.internal.logging.SLF4JLogger.debug(SLF4JLogger.java:67)]
connection: close
2016-05-10 19:38:09,640 (Twitter Stream
consumer-1[Establishing connection]) [DEBUG -
twitter4j.internal.logging.SLF4JLogger.debug(SLF4JLogger.java:67)]
Unknown URL. See Twitter Streaming API documentation at http://dev.twitter.com/pages/streaming_api
2016-05-10
19:41:11,961 (Twitter Stream consumer-1[Establishing connection]) [INFO

twitter4j.internal.logging.SLF4JLogger.info(SLF4JLogger.java:83)]
404:The URI requested is invalid or the resource requested, such as a
user, does not exist.
Unknown URL. See Twitter Streaming API documentation at http://dev.twitter.com/pages/streaming_api

andypiper · 2016-05-11T00:56:09.906Z

@umersafeer this thread is old and not related to the issue you raised elsewhere. It doesn’t help much to ask the same things on multiple threads. Have you tried the debugging steps I suggested? Closing this out now.

andypiper · 2016-05-11T00:56:13.839Z