There is no way to remove or cancel a camapaign that have been interefered ina away, for example if the app restarted (on localhost) or error happened.
Definitely sounds strange. Would you mind sharing the exact version of the package you are running? Also please make sure to upgrade.
You could set the log level to "debug" for a while to see if the debug logs give you any hints.
It would also be interesting to know if there are any items in the queue for the campaigns that is stuck in "Sending". It might be that one Campaign is in some kind of strange error-loop that stops others from continue.
Yes, there were some campaigns stuck because our integration is in development and some changes made the campaigns stuck. However we now removed all of them from the database so this won't be a major issue.
I just wanted to flag there is no other way to remove a stuck campaign other than deleting from the database.
Also I noticed that the campaign keeps showing "Sending" if the number of receivers is 0. I imagine that it should still complete/show as completed in the backoffice - even if there were no recipients to send the campaign to?
I understand, if a campaign gets stuck this is a symptom of some underlying issue that needs to be addressed by someone technical. This should be rare in production scenarios and most of the time it requires someone with technical skills to investigate. The scenarios look different and a generic "fix stuck campaign"-button is not really a simple thing to add as each type of issue has different underlying reasons.
I would encourage you to look at logs and error messages to understand why this is happening - a common source of problems is the underlying SMTP server that throws errors that bubble up to the package.
I would need more details to be able to help you, like error message, exact version etc. so if you need help investigating please provide this information.
No way to remove or cancel a campaign if sending hve been interefered
There is no way to remove or cancel a camapaign that have been interefered ina away, for example if the app restarted (on localhost) or error happened.
It is just hanging and keep disaplying "Sending".
Is this interntional?
Hi!
Yes, this is intentional since it will resume where it stopped if a restart happens.
If you really need to stop the send out you can manually remove the campaign and the queue items from the database.
More details about the db here: https://www.newsletterstudio.org/documentation/package/10.0.0/develop/database-tables/
// m
It never resumes
There is a background job that should start when the web site starts and pickup any campaigns that’s in progress.
Do you see any errors or warnings in the logs? Check during startup and maybe the first 5-10 minutes after start up.
It does resume in some cases, in some cases it doesn't and we can't see any NS errors in the log.
Hi!
Definitely sounds strange. Would you mind sharing the exact version of the package you are running? Also please make sure to upgrade.
You could set the log level to "debug" for a while to see if the debug logs give you any hints.
It would also be interesting to know if there are any items in the queue for the campaigns that is stuck in "Sending". It might be that one Campaign is in some kind of strange error-loop that stops others from continue.
Is this from your production environment?
// m
Yes, there were some campaigns stuck because our integration is in development and some changes made the campaigns stuck. However we now removed all of them from the database so this won't be a major issue. I just wanted to flag there is no other way to remove a stuck campaign other than deleting from the database.
Also I noticed that the campaign keeps showing "Sending" if the number of receivers is 0. I imagine that it should still complete/show as completed in the backoffice - even if there were no recipients to send the campaign to?
Hi!
I understand, if a campaign gets stuck this is a symptom of some underlying issue that needs to be addressed by someone technical. This should be rare in production scenarios and most of the time it requires someone with technical skills to investigate. The scenarios look different and a generic "fix stuck campaign"-button is not really a simple thing to add as each type of issue has different underlying reasons.
I would encourage you to look at logs and error messages to understand why this is happening - a common source of problems is the underlying SMTP server that throws errors that bubble up to the package.
I would need more details to be able to help you, like error message, exact version etc. so if you need help investigating please provide this information.
is working on a reply...