Start with the sequence before searching for edge cases
Most NexaMail problems come from missing prerequisites rather than obscure bugs. That is why the fastest troubleshooting path usually starts with dependencies: subscription, sender verification, list readiness, import health, and campaign configuration.
| Problem | What to check first | Why that check matters |
|---|---|---|
| Subscription page keeps returning | Confirm the plan is active and payment is complete. | The app may block later actions until billing is fully resolved. |
| Sending domain stays pending | Recheck DNS type, host, and value, then allow for propagation. | Most domain issues come from small DNS mistakes or impatience. |
| Verified sender error during campaign setup | Check that the chosen sender email belongs to a verified identity. | Campaigns often fail when the sender configuration does not match the verified setup. |
| Import does not finish | Review file structure and import progress or background processing. | Large imports may still be running even when the upload step is complete. |
| Campaign cannot send | Check recipients, sender details, subject line, and schedule. | Most send blocks happen because one required part of the campaign is incomplete. |
| No reporting appears after send | Check tracking settings and give the campaign time to collect activity. | Reporting usually needs tracking enabled and enough elapsed time to populate. |
Use a simple diagnostic order
- Check subscription status first.
- Check sender verification next.
- Check that the list or segment is available and correct.
- Check whether imports or background jobs are still running.
- Check campaign content and final confirmation settings last.
Practical principleIf something worked previously and then stopped, compare what changed: the list source, the sender identity, the DNS records, the content, or the schedule settings.