Can we create Media template with using Resumable Upload API of Meta, if we have the https url of the media

We wanted the create media template using meta cloud api without using resumable upload api.

eg payload : { "category": "MARKETING", "name": "flig_confim", "language": "en", "allow_category_change": true, "components": [ { "type": "BODY", "text": "This is your flight confirmation for {{1}}-{{2}} on {{3}}", "example": { "body_text": [ [ "Delhi", "Banglore", "20th Monday" ] ] } }, { "type": "FOOTER", "text": "To manage the reservation signin to travel portal" }, { "type": "HEADER", "format": "IMAGE", "example": { "header_handle":"4::YX..." } } ] }

Below is the example to create media template with header_handle info got during resumable api. But we wanted to create media tempate without using resumable api, where user will provide the https url of the image/document and we need to create template using that link instead of header_handle

We use a webhook to receive comments that mention users who have authenticated via our app, this has worked for years. Now, since 8/28 the username field of the commenter mentioning the authenticated user is no longer being returned in the comment data.
We are using Facebook Login for Business with the instagram_manage_comments permission, which according to this documentation is correct:
https://developers.facebook.com/docs/instagram-platform/instagram-graph-api/reference/ig-comment
We are seeing in the developer community site other people are having this issue.

Hi everyone,
Since 19:20 Bangkok time today, I've been encountering an issue when trying to send images via the Messenger API. I'm receiving the following error:
'code': 100,
'error_subcode': 2018047
This error occurs when I attempt to send an image using an S3 URL that has worked without issues for a long time. Here's an example of the API request body I'm using (with sensitive data hidden):
{
"message": {
"attachment": {
"payload": {
"url": "https://.s3.ap-southeast-1.amazonaws.com/.jpeg"
},
"type": "image"
}
},
"messaging_type": "MESSAGE_TAG",
"recipient": {
"id": ""
},
"tag": "CUSTOMER_FEEDBACK"
}
This has been working fine until today, and I'm not sure what's causing the sudden issue. Has anyone else experienced this or knows what might be going on? Any insights or advice would be greatly appreciated.
Thank you!