Are Reoccurring Notifications/ Marketing Messages still in Beta? I tried sending an opt In message in Instagram and received '(#10) This account is not eligible for the Recurring Notification IG Beta' but support forums say beta was supposed to be done in 2022!

Hi all,
We have been using the Send Messages API with template buttons at https://graph.facebook.com/v18.0/me/messages.
I received an error with the following details: Code: 100, SubCode: 2018023, fbtraceId: AlJOcqaDk5993l2-k7v0o8o, msg: (#100) Save attachment failure.
The error occurred only for PSID 4822705404446239; the others were successful without errors.
session_id: https://developers.facebook.com/tools/explorer/1621755161178887/?session_id=944758980529968
Any idea or any reported bug as I didn't find any?

Is Messenger Platform Dead?
There is a confirmed bug we have found and wanted to create a bug report. However, we cannot create bug report for any of the Messenger related category. It kept showing as the error like that.
Are you guys stopped supporting the Messenger Platform?

I have a test application with a verified webhook and a connected test user in the Meta developers console. The webhook has two subscriptions: messages and messaging_postbacks. The webhook receives the messages callbacks but doesn't receive postbacks when the test user clicks postback buttons in the chat.Could you please tell what is the problem?
In the same time it receives test messaging_postbacks from the developer console.

We are receiving the "User consent is required to access user profile" for users who are directly messaging a business.
As an example, using a webhook for the incoming message:
{
"object": "instagram",
"entry": [
{
"time": 1710698073629,
"id": "17841401619523691",
"messaging": [
{
"sender": {
"id": "7258088794280671"
},
"recipient": {
"id": "17841401619523691"
},
"timestamp": 1710698073342,
"message": {
"mid": "REDACTED",
"text": "Kit"
}
}
]
}
]
}
Making a request to:
https://graph.facebook.com/v19.07258088794280671?access_token={PAGE_TOKEN}
s returning the error