Two MailPoet releases landed a week apart, so this note covers both. Between them they fix a background job problem that was quietly stopping bounce processing and WooCommerce sync, connect tracking preferences with AutomateWoo, and get pop-up and slide-in forms showing on sites where they had gone missing.
One failing background job no longer stops the rest. Before 5.38.0, a single job that failed to start would halt the ones queued behind it, so bounce processing and WooCommerce sync could stop with no warning. Each job now runs on its own. The same release corrects the Amazon SES region list to match AWS: seven regions added, China (Ningxia) now reaching the right AWS China endpoint, and Hong Kong and China (Beijing) removed because SES does not run there. Personalization tags also stop showing HTML-encoded characters in subject lines and plain-text emails, so subject lines read as written.
A subscriber only has to state a tracking preference once. In 5.38.1, turning off open and click tracking in MailPoet also turns it off in AutomateWoo, and turning it back on clears it in both places. The same release fixes pop-up, fixed bar, and slide-in forms that were not appearing on single posts and pages when a theme or page builder renders the content outside the main loop. Bulk unsubscribing a large selection of subscribers now finishes instead of timing out, the Emails page loads on stores with a large log table, and exported subscriber and statistics values that a spreadsheet reads as a formula, such as a phone number starting with a plus sign, come through intact. In the block email editor, social icons render correctly, the Personalization Tags button is back on Button blocks, and Back button sizing is fixed on WordPress 7.1.
How to get it
Update to MailPoet 5.38.1 from your WordPress dashboard — Plugins > Installed Plugins, or WooCommerce > Extensions. If you are on 5.38.0 already, updating again picks up the second release. One thing to check: if you send through Amazon SES using Hong Kong or China (Beijing), review your sending configuration — those regions have been removed from the list.