The "Auto resume broadcasts" is not working

hwp994108018

Beginner
Greetings,
My question is in 2 parts: The "Auto resume broadcasts" is not working, details about cron setting

1. I have enabled Broadcast Settings-Auto resume broadcasts upon connection reestablishment, Recheck auto-inactive sending node connection after every 5 Minutes, Recheck auto-inactive sending node connection for 120 Hours, and according to this post, mumara was optimized in a few days ago: https://community.mumara.com/threads/memory-allocation.228/#post-865, but the System paused Broadcast did not automatically resume sending,, Even after 12 hours, "System paused" is still "System paused."
For php.ini
memory_limit = 512M
max_execution_time = 300 # Although it shouldn't matter as almost all operations run in the background. Set it your own way. If you are uploading larger files, you would need to increase it.
max_input_time = 900
max_input_vars = 100000
post_max_size = 50M # It's totally your own choice. I don't know the maximum filesize of the list your are importing

For my.cnf
innodb_buffer_pool_size=2G

My server: 2CPUs, 4g ram

2. I found this post does not explain all the cron function: https://support.mumara.com/hc/articles/35/cron-settings
For example, what is "Pending Stats ""Stucked Campaigns" "Evergreen Campaigns "??

Thank you for your time,
Huang
 
Hi,

Here are the answers to your queries

1- Please check the status of your Sending node. If the Sending node is inactive, any scheduled campaigns will remain in the system paused status.

2- I will explain the Cron Command
Pending Stats: This command will process the data in the table "stats_pending" & in the "stats_pending" table including data like injected, delayed, delivered, bounced, spammed, etc.
Stucked Campaigns: This command will check if any scheduled campaign whose status is processing & stuck due to a server down or any other reason then that campaign will start sending an email.
Evergreen Campaigns: This command is used to schedule Evergreen Campaigns.

NOTE: We'd love to hear your feedback! Please leave us a review on [Trustpilot](https://www.trustpilot.com/review/www.mumara.com) and [G2](https://www.g2.com/products/mumara/reviews), and receive our Evergreen addon for free, for life!
 
Hi,

Here are the answers to your queries

1- Please check the status of your Sending node. If the Sending node is inactive, any scheduled campaigns will remain in the system paused status.

2- I will explain the Cron Command
Pending Stats: This command will process the data in the table "stats_pending" & in the "stats_pending" table including data like injected, delayed, delivered, bounced, spammed, etc.
Stucked Campaigns: This command will check if any scheduled campaign whose status is processing & stuck due to a server down or any other reason then that campaign will start sending an email.
Evergreen Campaigns: This command is used to schedule Evergreen Campaigns.

NOTE: We'd love to hear your feedback! Please leave us a review on [Trustpilot](https://www.trustpilot.com/review/www.mumara.com) and [G2](https://www.g2.com/products/mumara/reviews), and receive our Evergreen addon for free, for life!

1- Please check the status of your Sending node. If the Sending node is inactive, any scheduled campaigns will remain in the system paused status.
Simple answer is "sendin node is active ".
When the campaigns became "system paused ", I had checked the sending node several times and it was "active", I even rechecked it again through the "test connection" and it was "active". It's so strange.

Besides, like I said before, I have enabled Recheck auto-inactive sending node connection after every 5 Minutes, Recheck auto-inactive sending node connection for 120 Hours. If the sending node "auto inactive" for some reason,the sending node will also be automatically rechecked and started, right?


2- I will explain the Cron Command
Actually, I would like to know about cron function, plus if you can update this page: https://support.mumara.com/hc/articles/35/cron-settings ? This will help all users

Thank you for your time,
Huang
 
1- I suggest you submit a support ticket from your client area & the support team will look into the matter.

2- We are already working on updating the whole documentation which will be updated soon.
 
Back
Top