-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix test sending for ActiveCampaign #974
Comments
From SMDP:
@miguelpeixe is there any chance that we could prioritize this? With more folks signing on to BlueLena, we're seeing more desire to use Newsletters. Having a functional testing process would be splendid. |
Once #992 is released the occasional In case the error message is:
, there's nothing we can do on our end. This is an API restriction imposed by ActiveCampaign on that account. The test campaign will be created but only possible to send through their web interface. |
Is this a restriction on ALL accounts? Or just the one that we're using for testing? |
Not sure. I guess it's a restriction for new accounts, which might lack some verification. |
As previously reported, a test email goes to AC, but sits there waiting to be sent manually. I can't find the issue, but it was talked about extensively in Slack.
Even this is inconsistent; a recent demo didn't produce a test email at all.
Also, when my test email did land in AC, it was ready to send to the 17 people in the email list I'd chosen from the dropdown. As far as I know, the test should be independent of any list chosen -- and certainly shouldn't be sent out to a full list. It was never scheduled or ready to send to the one email I'd listed in the "send a test to" field. So in that regard, I'm GLAD it didn't send.
This work was done on Model Home, which is set up to work with out AC test account.
The text was updated successfully, but these errors were encountered: