Currently, when a message fails to send due to Meta delivery issues (like the error: "Meta did not deliver message"), there is no notification or trigger to let us know. These failures happen silently-without alerts, tags, or error events-making it easy to miss leads or conversations that didn't go through.

Request:
Please add a way to trigger an action or notification when a message fails. This could include:

• A system event for failed delivery (usable in flows or conditions)

• An automation trigger for failed messages

• The ability to apply a tag or send an internal notification

• Even just logging failed messages to a specific place in real time

Why it matters:
This is crucial for customer support, lead follow-ups, and reliable automation. Right now, we only catch failures manually by digging through history. A simple failure trigger would make ManyChat flows far more dependable and proactive.