Title: Upgrade error
Last modified: June 28, 2026

---

# Upgrade error

 *  Resolved [wpkiller](https://wordpress.org/support/users/wpkiller/)
 * (@wpkiller)
 * [1 week ago](https://wordpress.org/support/topic/upgrade-error-34/)
 * After upgrading to v5.32, the WordPress admin panel shows (in somewhat Yello 
   background frame):
 * Migration “MailPoet\Migrations\Db\Migration_20260610_120000_Db” failed. Details:
   An exception occurred while executing a query: Duplicate key name ‘segment_id_status’

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Support [Gui A. a11n](https://wordpress.org/support/users/guicmazeredo/)
 * (@guicmazeredo)
 * [4 days, 18 hours ago](https://wordpress.org/support/topic/upgrade-error-34/#post-18952397)
 * Hi there,
 * This error means the database index `segment_id_status` already exists on one
   of MailPoet’s tables, so when the v5.32 migration tries to create it again, it
   runs into a conflict. This can happen if a previous update attempt partially 
   completed.
 * Here are two options to resolve it, starting with the simplest:
 * **Option A — Re-install the plugin via FTP**
 * Follow [these instructions](https://kb.mailpoet.com/article/258-re-installing-updating-the-plugin-via-ftp)
   to re-install the plugin via FTP and see if the migration completes.
 * **Option B — Drop the duplicate index manually (if Option A doesn’t help)**
 * You’ll need access to your database via phpMyAdmin (most hosts provide this in
   your hosting control panel):
    1. Back up your database first.
    2. Open phpMyAdmin and select your WordPress database.
    3. Run this SQL query (adjust the table prefix if yours is different from `wp_`):
 *     ```wp-block-code
       DROP INDEX segment_id_status ON wp_mailpoet_subscriber_segment;
       ```
   
    4. Then go back to **Plugins**, deactivate MailPoet, and reactivate it. The migration
       should now run successfully and recreate the index properly.
 * If you’re not comfortable running SQL queries directly, your hosting provider’s
   support team should be able to help with this — just share the query above with
   them.
 * Let us know if either of these resolves it!
 *  Thread Starter [wpkiller](https://wordpress.org/support/users/wpkiller/)
 * (@wpkiller)
 * [2 days, 20 hours ago](https://wordpress.org/support/topic/upgrade-error-34/#post-18954490)
 * As I was already on v5.33, I’ve rolled back with a plugin to v5.31 and then reupdate
   to v5.33 and all went well.
 * I hope it means everything is ok now.
 *  Plugin Support [Gui A. a11n](https://wordpress.org/support/users/guicmazeredo/)
 * (@guicmazeredo)
 * [2 days, 19 hours ago](https://wordpress.org/support/topic/upgrade-error-34/#post-18954551)
 * Hey [@wpkiller](https://wordpress.org/support/users/wpkiller/),
 * It’s great to hear everything seems to be working again. Thanks for sharing the
   steps you’ve take to fix it. This can be useful for other users experiencing 
   similar issues in the future.
 * I’m marking this thread as resolved, but don’t hesitate to contact us again if
   you need any assistance.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fupgrade-error-34%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/mailpoet/assets/icon-256x256.png?rev=3284564)
 * [MailPoet - Newsletters, Email Marketing, and Automation](https://wordpress.org/plugins/mailpoet/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/mailpoet/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/mailpoet/)
 * [Active Topics](https://wordpress.org/support/plugin/mailpoet/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/mailpoet/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/mailpoet/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Gui A. a11n](https://wordpress.org/support/users/guicmazeredo/)
 * Last activity: [2 days, 19 hours ago](https://wordpress.org/support/topic/upgrade-error-34/#post-18954551)
 * Status: resolved