Posts under category Meta & Facebook

when using the /pages/search with the query "minnesota zoo", I expect the following page to be included in the search result:
URL: https://www.facebook.com/mnzoo Page Name: Minnesota Zoo Page ID: 136257148787
The search results include a different unofficial page with the same name, so I would expect the page above to be included as well.
Please let me know if you need any further information, thanks

Recently, we've found out that during conversation with user and the Facebook Page on Messenger we're getting some unexpected results regarding author of the message. It looks like for some users, instead real name, we're getting Facebook user.
"from": {
"name": "Facebook user",
"email": "[...]",
"id": "{ID}"
}
What is the reason of changing author name to Facebook user? We need to inform clients why it's happening.

Error validating access token: The application does not belong to system user's businessor its aggregators's business
"error": {
"message": "Error validating access token: The application does not belong to system user's businessor its aggregators's business",
"type": "OAuthException",
"code": 190,
"error_subcode": 465,
"fbtrace_id": "AwdeeckPQClEJZ817B1FMvg"
}

This specifically seems to affect post_video_ad_break_ad_impressions, post_video_ad_break_earnings and post_video_ad_break_ad_cpm under Page insights -> Video Ad Breaks metrics.
A request in the form of
GET [page_id]/insights?metric=post_video_ad_break_earnings&period=day&since=1711954800&until=1714460400
returns
{
"data": [
],
"paging": { ... }
}
This doesn't change based on whether the period is set to day, lifetime or omitted. Similarly, it doesn't change with the value of since nor until, nor does it change if they are omitted.
When mixed in with other (older?) metrics, which work in isolation, either no data is returned for the affected metrics, or only data for unaffected metrics is returned, which seems to vary request to request (i.e. the same request may produce varying results when repeated).
This seems to affect multiple pages, authenticated by multiple users.
Question: am I doing something wrong? Am I omitting some parameter that is not (well) documented?
Due to the random interactions with other metrics this feels like a bug, but there no longer exists a path to report a bug in this product.