Forwarding cross-posted messages results in a 500 error

[hampuskraft]

Description

Forwarding a cross-posted message from a followed announcement channel causes a 500.

Note

The prerequisites for a cross-posted message to fail when being forwarded are unknown. I have found numerous example messages that result in a 500 error; see my comment below for details.

Steps to Reproduce

1. Locate a cross-posted message that was published from a followed announcement channel.
2. Attempt to forward the message by sending a new message, either via the API or the client.

curl -X POST https://discord.com/api/v9/channels/<CHANNEL_ID>/messages \
-H 'Content-Type: application/json' \
-H 'Authorization: <AUTH_TOKEN>' \
-d '{"message_reference":{"guild_id":"<GUILD_ID>","channel_id":"<REFERENCED_CHANNEL_ID>","message_id":"<MESSAGE_ID>","type":1}}'

Expected Behavior

The message is successfully forwarded to the target channel without any errors.

Current Behavior

The operation fails with a 500 Internal Server Error response.

Screenshots/Videos

No response

Client and System Information

Reproducible on the latest Stable and Canary versions of the API.

[hampuskraft]

This appears fixed as of a recent API deploy.

[hampuskraft]

Re-opening this issue as it persists for specific messages. For example, an engineer can likely reproduce it by attempting to forward a copy of the message with channel_id=617201058502148096 and message_id=1316858857133178981. I have been informed that this is a known internal issue, but keeping this issue open could help prioritize it and prevent duplicate reports. I’m happy to provide any additional details that may help resolve it.