# Microsoft Teams publisher issue

**URL:** <https://www.finalbuilder.com/forums/t/microsoft-teams-publisher-issue/7795>\
**Category:** Bugs\
**Created:** [June 3, 2026, 4:18pm UTC](https://www.finalbuilder.com/forums/t/microsoft-teams-publisher-issue/7795 "2026-06-03T16:18:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rjantz](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/r/ed8c4c/32.png) [@rjantz](https://www.finalbuilder.com/forums/u/rjantz)\
**Post date:** [June 3, 2026, 4:18pm UTC](https://www.finalbuilder.com/forums/t/microsoft-teams-publisher-issue/7795/1 "2026-06-03T16:18:48Z")

</div>

I have a Microsoft Teams publisher set up to publish a Message card to a webhook and it does work but every time a message is sent there’s an error that is raised in the private messages saying “An error occurred while sending a Teams message. The response status code was Accepted. publisher plugin ‘Teams’. Discarding message”.

---

<div class="post-metadata">

**Author:** ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)\
**Post date:** [June 4, 2026, 6:07am UTC](https://www.finalbuilder.com/forums/t/microsoft-teams-publisher-issue/7795/2 "2026-06-04T06:07:04Z")

</div>

Hi @rjantz,

Thank you for reporting this. We can confirm that this is a bug.

Your Teams messages are being delivered successfully, but Continua is incorrectly treating the response from the webhook as a failure.

These newer Workflows/Power Automate webhooks return an `Accepted` response instead of `OK`, and Continua was only recognising `OK` as a successful response.

We’ve now fixed this so that `Accepted` is correctly recognised as a successful send, and the spurious error will no longer appear. The fix will be included in the next release.

In the meantime there’s no risk of duplicate or lost messages - your message cards are being delivered to Teams exactly once, and the publisher continues to work normally. The only side effects are the error entries in the log and the publisher showing an inflated error rate in its metrics, both of which will clear up once you upgrade.