NetSendo v1.7.10: Smarter Sending & Timezone Fixes

Have you ever scheduled a global campaign, only to find it reached your European users in the middle of the night? Or hit a daily sending limit on your email provider, leaving a chunk of your audience in the dark? These small issues can have a big impact on engagement and ROI.

At NetSendo, we believe that you should have full control over your marketing, and that includes overcoming these common hurdles. That’s why NetSendo v1.7.10 is all about enhancing reliability and precision. This update delivers two powerful features: a simple way to resend campaigns to failed subscribers and intelligent timezone handling for perfectly timed messages.

🚀 What's New in v1.7.10

This release targets two critical aspects of campaign management: recovering from delivery failures and ensuring your messages arrive at the right local time, every time.

One-Click Resend for Failed Messages

Message delivery can fail for many reasons—a temporary issue with the receiving server, or more commonly, hitting your sending provider's daily or hourly limits. Previously, retrying these required you to manually segment users and clone the campaign. Not anymore.

NetSendo v1.7.10 introduces a "Resend to Failed" button directly in your message statistics. With a single click, NetSendo automatically resets the status of all failed messages from failed back to planned. Your worker queue will then pick them up for another delivery attempt. It’s a simple, powerful way to maximize your reach and recover potentially lost conversions.

Intelligent Timezone Support for Scheduled Campaigns

As automation becomes more sophisticated, tools like our Marketing Control Plane (MCP) and external AI agents are used to schedule campaigns programmatically. A major challenge here is timezones. Sending a campaign scheduled for "9 AM" from a UTC-based server could mean it arrives at an inconvenient time for your audience.

ℹ️ Note: This fix is crucial for teams using our Marketing Control Plane (MCP) to orchestrate campaigns via external tools or AI agents.

This update introduces a robust, hierarchical timezone detection system. When a campaign is scheduled via the API, NetSendo now looks for a timezone in this order:

1. API Request: A timezone parameter explicitly passed with the request.
2. Campaign Settings: A timezone defined for the specific campaign.
3. User Profile: The timezone set in the profile of the user scheduling the message.
4. Default: Falls back to UTC if no other timezone is found.

This ensures maximum accuracy, giving you the confidence that your 9 AM campaign arrives at 9 AM, no matter where your subscribers are.

💡 Benefits & Use Cases

🛠️ Step-by-Step Guide

Ready to use these new features? First, make sure you've updated to the latest version:

# Pull the latest Docker image and restart your containers
docker compose pull
docker compose up -d

How to Resend to Failed Subscribers

1. Navigate to Message Statistics

   Open the campaign you want to check and go to its statistics view. You will see a summary of sent, delivered, and failed messages.

   [Image description: A screenshot of the NetSendo Message Statistics page, highlighting the 'Failed' count.]
2. Locate the 'Resend' Button

   If there are one or more failed messages, the "Resend to Failed" button will appear. If there are no failures, this button remains hidden.

   [Image description: A close-up of the "Resend to Failed" button, which is now visible and clickable.]
3. Confirm and Monitor

   Click the button and confirm your action in the dialog box. The failed messages will be re-queued, and you can monitor their progress in the message processing queue.

Scheduling with Timezone Awareness via API/MCP

For developers and power users, leveraging the new timezone feature is straightforward.

1. Update MCP Client (If Applicable)

   If you're using our MCP client package, be sure to update to the latest version to get support for the new parameter.

   npm install @netsendo/mcp-client@^1.3.0

2. Add the 'timezone' Parameter

   When making an API call to schedule a message, simply include the timezone parameter with a valid Olson timezone string (e.g., "Europe/Warsaw").

   {
     "campaign_id": 42,
     "subject": "Our Summer Collection is Here!",
     "send_at": "2026-06-21 10:00:00",
     "timezone": "America/Los_Angeles"
   }

   ⚠️ Important: If no timezone is provided in the request, NetSendo will fall back to the user's profile settings or UTC. Explicitly setting it is always best for critical, time-sensitive campaigns.

🎯 Expert Tips