Campaign stuck in sending and processing status

A

Ashish Shukla

Member
MailWizz 2.0 Tester
Hi,

Since last 2 days I noticed my campaigns stuck in sending and processing status. can anyone please help.
While I run cron manual it's going but not self.
I checked send-campaign cron runs in each minute but still not able to pickup campaigns those are in sending and Processing status.
I tried to clear mutex folder even after it's not running.
I need urgent help on this.
 
Same issue here right now. Completely out of the blue. Stuck at 69% for no reason. Only campaign running.
 
Hi @nadworks Somehow I solved this issue. What is the campaign Status, Sending or processing. Did you check number of parallel campaign, this might limit reached
 
Yes, tried all that. Thanks. It was stuck at 51% first. Then I increased the "send at once" from 200 to 500, which somehow pushed out a few more. Now it's been stuck at 69% and won't move. I've increased "send at once" to 1000 now, but that trick didn't seem to work a 2nd time.
 
Hi Guys,
I'm facing the same issue now, my campaign keep stuck at processing. My campaign run after I click on emergency actions from Backend > Misc > Emergency actions > Campaign Status. But it stuck again after a few minutes.
 
jaisonbaby said:
Same issue here right now. Completely out of the blue. Stuck at 21% for no reason
Click to expand...
www.mailwizz.com

Debug send campaigns command | MailWizz Email Marketing Documentation

Debug send campaigns command
www.mailwizz.com
I have tried this method. the result is

[2022-07-29 08:45:25] - Done for yyy@gmail.com, logging delivery...
[2022-07-29 08:45:25] - Logging delivery took: 0.02406
[2022-07-29 08:45:25] - xxx@gmail.com - 100/100
[2022-07-29 08:45:25] - Checking if we can send to domain of xxx@gmail.com...
[2022-07-29 08:45:25] - Checking if xxx@gmail.com is still confirmed...
[2022-07-29 08:45:25] - Checking if xxx@gmail.com is blacklisted...
[2022-07-29 08:45:25] - Checking if xxx@gmail.com is listed in a campaign suppression list...
[2022-07-29 08:45:25] - Checking if xxx@gmail.com is blocked in the campaign group...
[2022-07-29 08:45:25] - Checking if the server is over quota...
[2022-07-29 08:45:25] - Preparing the entire email...
[2022-07-29 08:45:25] - Parsed the tracking links from the html email content in 0.00015 seconds.
[2022-07-29 08:45:25] - Using delivery server: email-smtp.ap-southeast-1.amazonaws.com (ID: 193).
[2022-07-29 08:45:25] - Logging into delivery server usage log took: 0.01357
[2022-07-29 08:45:25] - Sending the email to the delivery server...
[2022-07-29 08:45:25] - Communication with the delivery server took: 0.24815
[2022-07-29 08:45:25] - Sending response is: OK
[2022-07-29 08:45:25] - Sending OK.
[2022-07-29 08:45:25] - Done for xxx@gmail.com, logging delivery...
[2022-07-29 08:45:25] - Logging delivery took: 0.01826
[2022-07-29 08:45:25] - Done processing 100 subscribers!
[2022-07-29 08:45:25] - Campaign status has been changed successfully!
[2022-07-29 08:45:25] - Done processing the campaign.
[2022-07-29 08:45:25] - This cycle completed in 37.92370 seconds and used 22 MB of memory!
[2022-07-29 08:45:25] - CPU usage in last minute: 4.99, in last 5 minutes: 2.82, in last 15 minutes: 2.65!
 
jaisonbaby said:
www.mailwizz.com

Debug send campaigns command | MailWizz Email Marketing Documentation

Debug send campaigns command
www.mailwizz.com
I have tried this method. the result is

[2022-07-29 08:45:25] - Done for yyy@gmail.com, logging delivery...
[2022-07-29 08:45:25] - Logging delivery took: 0.02406
[2022-07-29 08:45:25] - xxx@gmail.com - 100/100
[2022-07-29 08:45:25] - Checking if we can send to domain of xxx@gmail.com...
[2022-07-29 08:45:25] - Checking if xxx@gmail.com is still confirmed...
[2022-07-29 08:45:25] - Checking if xxx@gmail.com is blacklisted...
[2022-07-29 08:45:25] - Checking if xxx@gmail.com is listed in a campaign suppression list...
[2022-07-29 08:45:25] - Checking if xxx@gmail.com is blocked in the campaign group...
[2022-07-29 08:45:25] - Checking if the server is over quota...
[2022-07-29 08:45:25] - Preparing the entire email...
[2022-07-29 08:45:25] - Parsed the tracking links from the html email content in 0.00015 seconds.
[2022-07-29 08:45:25] - Using delivery server: email-smtp.ap-southeast-1.amazonaws.com (ID: 193).
[2022-07-29 08:45:25] - Logging into delivery server usage log took: 0.01357
[2022-07-29 08:45:25] - Sending the email to the delivery server...
[2022-07-29 08:45:25] - Communication with the delivery server took: 0.24815
[2022-07-29 08:45:25] - Sending response is: OK
[2022-07-29 08:45:25] - Sending OK.
[2022-07-29 08:45:25] - Done for xxx@gmail.com, logging delivery...
[2022-07-29 08:45:25] - Logging delivery took: 0.01826
[2022-07-29 08:45:25] - Done processing 100 subscribers!
[2022-07-29 08:45:25] - Campaign status has been changed successfully!
[2022-07-29 08:45:25] - Done processing the campaign.
[2022-07-29 08:45:25] - This cycle completed in 37.92370 seconds and used 22 MB of memory!
[2022-07-29 08:45:25] - CPU usage in last minute: 4.99, in last 5 minutes: 2.82, in last 15 minutes: 2.65!
Click to expand...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9410 pre-checks: Starting...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9410 pre-checks: Populating customer data...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9410 pre-checks: Pre-counting campaign subscribers...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9410 pre-checks: Pre-counting campaign subscribers, start counting...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9410 pre-checks: Pre-counting campaign subscribers, finished counting in 0.00381 seconds...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9410 pre-checks: Finding campaign max subscribers count and adjusting quota left...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9410 pre-checks: Currently quota left is 9223372036854775807 and campaign available subscribers for this batch is 0...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9410 pre-checks: Done!
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9411 pre-checks: Starting...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9411 pre-checks: Populating customer data...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9411 pre-checks: Pre-counting campaign subscribers...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9411 pre-checks: Pre-counting campaign subscribers, start counting...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9411 pre-checks: Pre-counting campaign subscribers, finished counting in 0.00271 seconds...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9411 pre-checks: Finding campaign max subscribers count and adjusting quota left...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9411 pre-checks: Currently quota left is 9223372036854775807 and campaign available subscribers for this batch is 0...
[2022-07-29 09:08:24] - [Worker 0] Campaign id 9411 pre-checks: Done!
 
@jaisonbaby - as I can see from your output, campaign is finished:
Code: 
[2022-07-29 08:45:25] - Campaign status has been changed successfully!
[2022-07-29 08:45:25] - Done processing the campaign.
[2022-07-29 08:45:25] - This cycle completed in 37.92370 seconds and used 22 MB of memory!
[2022-07-29 08:45:25] - CPU usage in last minute: 4.99, in last 5 minutes: 2.82, in last 15 minutes: 2.65!

If you go on campaign overview how many Recipients you have? Because grid data are cached and this can be the reason why you see another status that sent.
 
This keeps happening. No other campaigns running in parallel, low numbers so defo nowhere near any limits. Occasionally it helps to pause/unpause. But not always and it takes a number of such attempts to "unstuck" it. Scheduled campaigns can therefore be missed as nobody's watching progress.
Is this something that can be investigated somehow - or at least create an email alert "your campaign X has not yet reached 100% after XX minutes inactivity"?
 
You must log in or register to reply here.
Back
Top