Scoped_timeline endpoint - "User [user id] was not found" error

[Or_Rivery]

Hi Guys,

I’m trying to paginate through the scoped_timeline endpoint for a certain account and I keep getting this error:
{u’errors’: [{u’message’: u’User [user id] was not found’, u’code’: u’NOT_FOUND’}]
( [user id] = some user id, always the same one e.g: 1234567)

the pagination works for 3 calls then fails on the 4th (always on the same cursor)
Other accounts work just fine.

General call details:
url : https://ads-api.twitter.com/3/accounts/[account_id]/scoped_timeline
params: {‘count’: 1000, ‘cursor’: [cursor_id]}

Any thoughts on why this happens and how to fix it?

Thanks,
Or

[Or_Rivery]

error code: 403

[juanshishido]

Thanks for the message, @Or_Rivery.

Could you please share the account ID? See our Guidelines for Reporting Issues for more details on including the account ID in your inquiry.

[Or_Rivery]

Yes off course,
After reading the guidelines I realize I was a bit overprotective with that information.
the account id is: 18ce54odpk1

[Or_Rivery]

@juanshishido
Any new info regarding this issue?

[juanshishido]

Thanks for the follow up, @Or_Rivery. We been able to reproduce this and are starting to look into what the issue might be. We’ll update this thread once we know more.

[Or_Rivery]

That’s great,
Looking forward to your input @juanshishido

[Or_Rivery]

Hi @juanshishido
Any updates?

[juanshishido]

@Or_Rivery: We’re working on a fix. We’ll let you know once it’s been deployed.

[KickstoneMusic]

We also started experiencing this issue this week. Our AccountId is u0488

[juanshishido]

@Or_Rivery: The fix for this is now in production. Thanks again for taking the time to report the issue.

[Or_Rivery]

That’s great.
Thanks

[system]

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.