/search/tweets is failing to return a user object


#1

I’m seeing a high rate of failure for the /search/tweets request. Tweets are being returned with no user object. This is intermittent. It varies from about 1% to 10% of the responses have this problem. Here is an example of a tweet found with this call that had no user object.

stdClass Object
(
[metadata] => stdClass Object
(
[result_type] => recent
[iso_language_code] => en
)

[created_at] => Sun Jul 14 21:07:50 +0000 2013
[id] => 356520438198829056
[id_str] => 356520438198829056
[text] => poached salmon rolls from whole foods #healthy #sushi #myfirsttime #letsseehowthisgoes #wholefoods http://t.co/i1NXi5Ktlk
[source] => <a href="http://instagram.com" rel="nofollow">Instagram</a>
[truncated] => 
[in_reply_to_status_id] => 
[in_reply_to_status_id_str] => 
[in_reply_to_user_id] => 
[in_reply_to_user_id_str] => 
[in_reply_to_screen_name] => 
[geo] => 
[coordinates] => 
[place] => 
[contributors] => 
[retweet_count] => 0
[favorite_count] => 0
[entities] => stdClass Object
    (
        [hashtags] => Array
            (
                [0] => stdClass Object
                    (
                        [text] => healthy
                        [indices] => Array
                            (
                                [0] => 38
                                [1] => 46
                            )

                    )

                [1] => stdClass Object
                    (
                        [text] => sushi
                        [indices] => Array
                            (
                                [0] => 47
                                [1] => 53
                            )

                    )

                [2] => stdClass Object
                    (
                        [text] => myfirsttime
                        [indices] => Array
                            (
                                [0] => 54
                                [1] => 66
                            )

                    )

                [3] => stdClass Object
                    (
                        [text] => letsseehowthisgoes
                        [indices] => Array
                            (
                                [0] => 67
                                [1] => 86
                            )

                    )

                [4] => stdClass Object
                    (
                        [text] => wholefoods
                        [indices] => Array
                            (
                                [0] => 87
                                [1] => 98
                            )

                    )

            )

        [symbols] => Array
            (
            )

        [urls] => Array
            (
                [0] => stdClass Object
                    (
                        [url] => http://t.co/i1NXi5Ktlk
                        [expanded_url] => http://instagram.com/p/bwsf-QyhgB/
                        [display_url] => instagram.com/p/bwsf-QyhgB/
                        [indices] => Array
                            (
                                [0] => 99
                                [1] => 121
                            )

                    )

            )

        [user_mentions] => Array
            (
            )

    )

[favorited] => 
[retweeted] => 
[possibly_sensitive] => 
[lang] => en

)

I have the following parameters set in the API call:
‘result_type’ => ‘recent’, ‘lang’ => ‘en’, ‘include_entities’ => ‘true’, ‘count’ => 100

This code has worked with no problems in the past.


#2

Thanks for the report, Adam.


#3

This may be a transient problem. I’m still getting missing user objects with /search/tweets, but at a much lower rate (< .1%). I don’t know your internal architecture, but I’m guessing that the cluster that delivers user info may have had some temporary problem.