# Make reason for 'error moving posts' visible in the interface

**URL:** https://meta.discourse.org/t/make-reason-for-error-moving-posts-visible-in-the-interface/393690
**Category:** Feature
**Created:** [January 16, 2026, 3:51pm UTC](https://meta.discourse.org/t/make-reason-for-error-moving-posts-visible-in-the-interface/393690 "2026-01-16T15:51:57Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [February 9, 2026, 10:34am UTC](https://meta.discourse.org/t/make-reason-for-error-moving-posts-visible-in-the-interface/393690/2 "2026-02-09T10:34:51Z")

</div>

I don’t think this is a #Contribute > Feature, but instead a #Contribute > Bug 😉

> <https://github.com/discourse/discourse/pull/37634>
>
> When moving posts to a new topic fails (e.g. title too short, missing required t…ags, duplicate title), the modal only shows a generic "There was an error moving posts." message. Users had to open browser dev tools and inspect the network response to find the actual reason for the failure.
> 
> Use \`extractError\` from \`ajax-error.js\` to extract the specific error message from the server's JSON response, falling back to the generic message when no details are available.
> 
> https://meta.discourse.org/t/393690
> 
> \*\*BEFORE\*\*
> 
> \<img width="1727" height="1461" alt="2026-02-09 @ 10 23 04" src="https://github.com/user-attachments/assets/2e5f8880-44c3-4734-92b8-f663ced64f25" /\>
> 
> \*\*AFTER\*\*
> 
> \<img width="1727" height="1461" alt="2026-02-09 @ 10 22 21" src="https://github.com/user-attachments/assets/8de939ef-8033-4672-ab21-1de04d1e4ec7" /\>

---

_[View the full topic](https://meta.discourse.org/t/make-reason-for-error-moving-posts-visible-in-the-interface/393690)._