debug_token sometimes returns empty data response
https://graph.facebook.com/v19.0/debug_token?input_token= randomly returns empty data array.
Tony-Marketing-API.cn is a vibrant community dedicated to Facebook, Meta,Google Ads api, app development, Instagram, and related technologies. It offers valuable bug solutions, troubleshooting cases, and problem-solving strategies shared by users. Stay updated with real-world solutions, development tips, and the latest trends in digital marketing and app development.
https://graph.facebook.com/v19.0/debug_token?input_token= randomly returns empty data array.
only difference from normal response is that that empty array response does not have this header Content-Encoding: zstd
tried with debug=all when returning empty data array "debug" field is not set at all ( it is set when request succeeds )
We have also noticed the same anomaly: https://developers.facebook.com/community/threads/1363475634337488/
We have also noticed the same anomaly: https://developers.facebook.com/community/threads/1363475634337488/
We have also noticed the same anomaly: https://developers.facebook.com/community/threads/1363475634337488/
We have also noticed the same anomaly: https://developers.facebook.com/community/threads/1363475634337488/
Also noticing this. Timeline in PST: ~1:50pm Feb 26th. Started at low volume and remained consistent ~10:10am Feb 27th. Dropped zero (no issues) ~ll:25am Feb 27. Ramped up to high volume, this is when it started getting really bad and our own monitoring detected it. It has been at this level since.
Currently, if I do 100 identical calls to this endpoint with the same user token I get a failure (empty data array) rate of between 56% and 73% which is quite bad. I've done about 5 tests with 100 calls each to get these results. Over the last hour.
Also noticing this. Timeline in PST: ~1:50pm Feb 26th. Started at low volume and remained consistent ~10:10am Feb 27th. Dropped zero (no issues) ~ll:25am Feb 27. Ramped up to high volume, this is when it started getting really bad and our own monitoring detected it. It has been at this level since.
Currently, if I do 100 identical calls to this endpoint with the same user token I get a failure (empty data array) rate of between 56% and 73% which is quite bad. I've done about 5 tests with 100 calls each to get these results. Over the last hour.
Also noticing this. Timeline in PST: ~1:50pm Feb 26th. Started at low volume and remained consistent ~10:10am Feb 27th. Dropped zero (no issues) ~ll:25am Feb 27. Ramped up to high volume, this is when it started getting really bad and our own monitoring detected it. It has been at this level since.
Currently, if I do 100 identical calls to this endpoint with the same user token I get a failure (empty data array) rate of between 56% and 73% which is quite bad. I've done about 5 tests with 100 calls each to get these results. Over the last hour.
Also noticing this. Timeline in PST: ~1:50pm Feb 26th. Started at low volume and remained consistent ~10:10am Feb 27th. Dropped zero (no issues) ~ll:25am Feb 27. Ramped up to high volume, this is when it started getting really bad and our own monitoring detected it. It has been at this level since.
Currently, if I do 100 identical calls to this endpoint with the same user token I get a failure (empty data array) rate of between 56% and 73% which is quite bad. I've done about 5 tests with 100 calls each to get these results. Over the last hour.
Ok, have had confirmation form a Meta contact that it's been fixed. My tests confirm that 100% of /token_debug calls now work.
Ok, have had confirmation form a Meta contact that it's been fixed. My tests confirm that 100% of /token_debug calls now work.