You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 7, 2022. It is now read-only.
I've been running the hosebird client for 1 month now and it's been working perfectly. Yesterday it missed a tweet and there was nothing in the log to suggest why. Due to this being a production issue I had to restart it immediately to get it working again.
I would like to be able to reproduce this issue, but have no idea how. I've now turned on debug and will monitor closely.
Have there been any other issues with the User Stream Endpoint missing a tweet?
BTW, I had 2 application running at the time, and 1 of them received the tweet.
The text was updated successfully, but these errors were encountered:
I'm guessing this had something to do with the message I'm getting today:
{"errors": [{"message": "The Twitter REST API v1 is no longer active. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview.", "code": 68}]}
I've been running the hosebird client for 1 month now and it's been working perfectly. Yesterday it missed a tweet and there was nothing in the log to suggest why. Due to this being a production issue I had to restart it immediately to get it working again.
I would like to be able to reproduce this issue, but have no idea how. I've now turned on debug and will monitor closely.
Have there been any other issues with the User Stream Endpoint missing a tweet?
BTW, I had 2 application running at the time, and 1 of them received the tweet.
The text was updated successfully, but these errors were encountered: