- Communauté
- Question
Starting yesterday we are seeing several instagram conversations returning a non valid timestamp:
"updated_time": "56454-04-04T18:29:15+0000"
This is the endpoint we are currently using: me/conversations?fields=id,updated_time&platform=instagram
It does not seem to be a widespread issue but the amount of affected accounts is quite important right now. Does anybody know if that is something already reported to Meta?
Thanks in advance!
same issue!
Same here
We're experiencing the same issue across all our accounts! This is quite critical! Examples: 56445-05-17T13:59:11+0000 56566-04-29T03:52:37+0000 56379-07-01T21:11:24+0000 ......
In our end the issue is becoming widespread after some days. We have an increasing amount of affected accounts. Could someone advise about what can be done to fix this issue?
Report error on this page: https://developers.facebook.com/support/bugs/1520664862167268/
Many thanks! May I ask how did you manage to open a ticket in their system? I tried but it's always redirecting me to this community forum.
Unfortunately, it is the same for me. Ticket was opened by someone else
updated_time is converted from epoch multiplied by 1000 (which is the microseconds) to "yyyy-MM-dd'T'HH:mm:ssZ" format. Hence the endpoint returns dates like "56567-07-04T18:40:44+0000"
"56567-07-04T18:40:44+0000" is 1722930892844000 as epoch. It should be "2024-08-06T07:54:52+0000" which is 1722930892844 as epoch.
- Read the date and convert to epoch
- If it is too big to be a regular date, divide it by 1000
Hey there!
Could someone advise over this issue? Looks like a pretty bad data consistency problem over some specific accounts and the format do not match an actual date.
Thanks!