Start with one controlled subscriber
A missing welcome email does not identify the broken step. A person may never have entered the workflow, may be waiting inside it, or may have reached a send step without receiving the message. Record the address you control, subscription time, expected entry event, and actual activity before changing anything. Use test addresses only; do not replay a customer list to diagnose one failure.
This is a documentation-based diagnostic plan. In our September 16, 2026 trial, we reached the automation setup dialog but did not open the workflow editor, activate an automation or send a welcome email. Trial features may differ from the Free plan; use the worksheet to record your own results.
Symptom to likely cause
Each row below restates a condition from MailerLite's help center, accessed 2 October 2026. It is a documentation map, not a record of our own sends; confirm the cause with one controlled subscriber before changing a live workflow.
| Symptom | Likely cause | Check in MailerLite |
|---|---|---|
| Form submitted, subscriber never enters the workflow | The automation was not Active when the form was submitted | Automation status at the submission time; the Activity tab for the test address |
| Existing subscriber added to the trigger group again, nothing happens | A subscriber cannot rejoin a group they already belong to; they must be removed first | Group membership, and the re-entry option (re-triggers at most once every 24 hours) |
| Double opt-in across several forms, the expected welcome does not fire | Only the automation connected to the form where the subscriber confirms is triggered | Which form the confirmation came from; MailerLite suggests a group-based trigger here |
| Subscriber signed up but received only the confirmation email | No emails other than the confirmation are sent to unconfirmed subscribers | Subscriber status: Unconfirmed versus Active |
| Imported subscribers did not start an Updated field workflow | The import option to start the workflow was not checked | Import settings: "Yes, the imported subscribers should start the automation workflow" |
| No new entries and no sends at all | The workflow is turned off; no subscribers are added and no emails are sent while it is inactive | Automation on/off state |
| Activity lists the subscriber as Failed | Plan limit for active subscribers reached, a deleted step, or an email step not saved properly | Failure reason in the Activity tab |
| Activity lists the subscriber as Canceled | Subscriber deleted, unsubscribed or bounced, or the main trigger was changed | Cancellation reason in the Activity tab |
Check the event the workflow actually expects
MailerLite documents that a form-triggered automation must be active when the form is submitted. A group trigger depends on joining the selected group; someone already in that group has not joined it again. Compare the test subscriber's event with the configured trigger before editing the email.
With double opt-in across several forms, MailerLite says only the automation linked to the form where confirmation happens is triggered. Its documentation suggests a group trigger for this situation. Confirm the desired grouping with one address before changing a production flow.
| Observed state | Next check | Evidence to retain |
|---|---|---|
| No workflow activity | Active state and matching entry event | Timestamp and trigger configuration |
| Entered but waiting | Delay and condition steps | Current step and intended wait |
| Send recorded but inbox empty | Recipient address and mailbox folders | Send status; do not assume delivery |
| Import did not enter | Import choices and trigger rules | Import settings and one test record |
Treat imports and re-entry as separate decisions
For an Updated field trigger, MailerLite documents an import option that controls whether imported subscribers start the workflow. Record that choice instead of assuming importing equals enrolling. Re-entry also has its own setting; enabling it changes who may receive the series again.
Our recommended acceptance cases are a new confirmed signup, an existing group member, a deliberately imported test subscriber, and a returning subscriber. Write the intended outcome before running each case. Change one setting at a time so the result remains interpretable.
Write the first welcome sequence before activating it
A first-welcome decision is different from repairing a live series. Write the entry condition, exclusion list, expected events, and receipt check before turning any automation on. Keep the current or free plan when a repaired trigger would meet the job; do not migrate because the sequence is still unwritten.
On 16 September 2026 the editorialdesk trial had groups Newsletter, Events, and Customers at 0 members, six authorized plus-address test subscribers, and no activated welcome automation. No welcome email was sent. Use fictional or operator-owned contacts only. Record: who should enter (new confirmed signup), the exclusion (existing Customers, unsubscribed, already-onboarded), the events to inspect (entered, waiting, send recorded), and the receipt (provider send status plus the test mailbox, kept separate).
Use an expected-result matrix before another test
Illustrative case: a workflow uses Joins a group, but the test address already belongs to that group. Submitting a form again does not establish another group-join event. First inspect membership and activity; then use a new address you control for the positive case. This is a worked diagnosis, not a recorded send or a reason to remove real subscribers from a group.
| Controlled case | Expected checkpoint | Decision |
|---|---|---|
| New confirmed signup with matching entry event | One workflow entry, then the configured steps | If entry is absent, investigate the trigger before the email |
| Existing member of the trigger group | No new group-join event established | Use a separate controlled address; do not replay the customer list |
| Workflow entry visible, send step not reached | Current wait or condition explains the delay | Check the configured timing before changing providers |
| Provider records a send | Inspect the controlled mailbox separately | Do not equate a send event with inbox receipt |
Decide whether the repair worked
Keep the production list unchanged until the controlled case enters the intended workflow once and reaches the expected step. A provider's send record and receipt in your test mailbox answer different questions; retain both when available. If you need support, share redacted timestamps and the failing step through the provider's support channel, never a full subscriber export.
If the current product can meet the requirement, a repaired trigger is usually a smaller project than migration. Revisit the tool choice only when the documented feature or your observed result cannot support the workflow.
Before opening MailerLite's product page below, write the missing requirement: number of active workflows, entry rule, or subscriber limit. Compare that requirement with the current plan details. If the controlled case works on your existing plan, retain it; a product click is for checking fit, not a recommendation to upgrade.
Questions before you decide
Should I rebuild the welcome automation?
Not until one controlled subscriber shows the failing step. Write the entry condition, exclusion list, expected events, and receipt check first. Keep the current tool when a repaired trigger would meet the job.
Did this publication send a welcome email?
No. On 16 September 2026 the editorialdesk trial opened the Create automation modal and did not reach the workflow editor. No automation was activated and no welcome email was sent.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- MailerLite automation triggers Accessed 2 Oct 2026
- MailerLite: subscription plan and billing Accessed 16 Sep 2026
- MailerLite: How to use double opt-in when collecting subscribers Accessed 2 Oct 2026
- MailerLite: Automations FAQ Accessed 2 Oct 2026
- MailerLite: How to use automation activity Accessed 2 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.