If you run Messenger automation and a send that used to work quietly started throwing errors in late April 2026, you're not imagining it. Meta didn't just deprecate a feature, it changed how the deprecation behaves, and that second change is what made a months-old problem suddenly visible.
This is a compliance story with two dates, not one, and the gap between them is why so many integrations only noticed the break in April despite the actual deprecation happening in February.
The Two-Stage Deprecation
February 9, 2026: Meta deprecated message tags on the Messenger Platform globally, with one exception (HUMAN_AGENT was left untouched). Requests using tags like CONFIRMED_EVENT_UPDATE, ACCOUNT_UPDATE, and POST_PURCHASE_UPDATE stopped being honored. Critically, Meta's own guidance at the time was that these messages "won't be sent, so the account won't be banned." No error, no crash, just a message that silently never arrived.
April 27, 2026: The same deprecated tags started returning error code 100 on the request itself. Nothing new was deprecated. What changed is that a silent failure became a loud one, which is exactly the kind of change that gets missed in a changelog and then discovered in production.
If your team patched around this in February because messages seemed to stop arriving, you were already ahead. If you didn't notice until April, you were dealing with the second-order effect of a first-order problem that had been live for two and a half months.
Why Meta Handled It This Way
Message tags existed to let businesses message someone outside Messenger's standard 24-hour customer-service window, for specific narrow reasons: confirming an event, flagging an account change, following up on a purchase. It was a convenience mechanism layered on top of the core rule that Meta's compliance model is built around: businesses shouldn't have open-ended permission to message people whenever they want.
Utility Templates and the Marketing Messages API replace that convenience with a stricter model. Instead of a free-text message plus a tag asserting why it's allowed, you submit a template for review, and Meta approves the category and wording ahead of time. It's slower to set up and less flexible, but it closes the loophole where any developer could just attach ACCOUNT_UPDATE to whatever they wanted to send.
What to Actually Migrate To
| Old mechanism | Replacement | Best for |
|---|---|---|
CONFIRMED_EVENT_UPDATE tag |
Utility Message Template | Transactional updates (bookings, confirmations) |
ACCOUNT_UPDATE tag |
Utility Message Template | Account status changes |
POST_PURCHASE_UPDATE tag |
Utility Message Template or Marketing Messages API | Order status, shipping updates |
| Any promotional use of a tag | Marketing Messages API | Sends outside the standard window, EU excluded |
The practical migration is: identify every place in your codebase that still attaches one of the deprecated tags, decide whether the message is transactional (Utility Template) or promotional (Marketing Messages API, where available), then submit templates for review before removing the old code path. Submitting templates first matters, because once you strip the deprecated tag without a replacement approved, those messages simply stop going out entirely.
For teams in the EU, this is more constrained. Marketing Messages aren't available there, which leaves Utility Templates and Recurring Notifications (also live in Australia, Japan, South Korea, and the UK) as the only two options. If your use case doesn't fit either category cleanly, that's worth flagging internally now rather than after a send starts failing.
Why This Doesn't Touch Instagram Comment-to-DM
Message tags exist specifically to message someone outside Messenger's standard 24-hour reply window. That's not how comment-to-DM automation works. Someone comments a keyword on a post, the automation replies, and that reply happens inside the normal window because it's a direct response to something the user just did on your content.
There's no proactive send happening days after the fact, no re-engagement message weeks later, and no reason to attach a message tag in the first place. UnlockDM's DM outbox has never touched CONFIRMED_EVENT_UPDATE, ACCOUNT_UPDATE, or POST_PURCHASE_UPDATE, because the entire mechanic is built around a fast, in-window reply to something the user initiated, not proactive outreach that needs a tag to justify itself.
That's not a coincidence so much as a structural difference. Tools that promise multi-day follow-up sequences or re-engagement broadcasts on Messenger are exactly the integrations that leaned on these tags, and they're the ones scrambling to migrate right now. A tool that only ever replies to an active comment thread never had the problem to begin with.
What This Means If You Run Multiple Automation Tools
Plenty of creators and brands run more than one messaging integration: an Instagram comment-to-DM flow alongside a separate Messenger or WhatsApp automation for customer service or order updates. This deprecation is a Messenger Platform change, so it's the second category of tool that needs attention, not the first.
If you're not sure whether a tool you use is affected, check whether it ever sends a message to someone who hasn't messaged you in the last 24 hours. If it does, and it isn't already using Utility Templates or the Marketing Messages API, it was relying on a message tag, and it's been broken since February whether anyone noticed or not.
This also explains why ManyChat and other automation platforms posted their own migration guidance around this deprecation. Anyone offering proactive re-engagement messaging on Messenger had to rebuild that piece of their product, which is a real engineering cost that a comment-triggered flow simply doesn't carry.
Checking If You're Affected
A quick audit before assuming you're fine:
Do you send Messenger messages outside a 24-hour reply window? If every message you send is a direct reply to something the user just did, you're not affected.
Did any automated message stop arriving in February without an obvious cause? That's the earlier, silent version of this same deprecation.
Are you seeing error code 100 on sends starting around late April? That's the hard-error phase, and it means whatever tag you were relying on needs a Utility Template or Marketing Messages API replacement now, not eventually.
Are you in the EU? Confirm which of Utility Templates or Recurring Notifications actually fits your use case, since Marketing Messages isn't an option there.
FAQ
What happened to Meta's message tags in 2026?
Meta deprecated the Messenger Platform's message tags globally. From February 9, 2026, tagged requests using CONFIRMED_EVENT_UPDATE, ACCOUNT_UPDATE, and POST_PURCHASE_UPDATE silently stopped sending. From April 27, 2026, the same requests started hard-erroring with error code 100 instead of failing quietly.
What is the CONFIRMED_EVENT_UPDATE or ACCOUNT_UPDATE error I'm seeing? It means your integration is still calling Meta's Send API with a deprecated message tag attached. Before April 27 these requests failed silently; after that date they return error code 100, which is why the error suddenly became visible even though the underlying tag stopped working months earlier.
How do I migrate away from message tags? Meta's recommended path is Utility Message Templates for transactional-style updates, or the Marketing Messages API for promotional sends. Both require pre-approved templates rather than a free-text message plus a tag, so migration means submitting templates for review before you can send again.
Does this affect Instagram comment-to-DM automation? Not directly. Message tags are a Messenger Platform mechanism for messaging someone outside the normal 24-hour reply window. Instagram comment-to-DM automation replies to a comment the user just made, which falls inside that standard window and never needed a message tag in the first place.
Is the Marketing Messages API available everywhere? No. Marketing Messages are not available in the EU. Businesses there are limited to Recurring Notifications (also available in Australia, Japan, South Korea, and the UK) or Utility Templates, which narrows the migration options for EU-based Messenger integrations specifically.
UnlockDM's comment-to-DM flow replies inside Instagram's standard messaging window every time, which is why this deprecation is a non-event for it. If you're spending this week migrating Messenger templates, that's exactly the kind of maintenance tax a comment-triggered flow was built to avoid.
