Troubleshooting

A. Check Port 25: Many ISPs block Outbound Port 25 by default. Switch to Port 587 (TLS) or 465 (SSL).

B. Verify Credentials: Ensure your SMTP password is correct. Note that for services like Gmail, you must use an "App Password," not your standard login password.

New AWS SES accounts are in the "Sandbox." This means you can only send mail TO verified email addresses or the SES simulator address.

To Fix: Go to the AWS SES Dashboard → Get Set Up → Request Production Access. Briefly describe your marketing strategy and Amazon will usually move you to production within 24 hours.

1. Ensure your Cloudflare Worker URL is correctly pasted in Vexifa Settings.
2. Verify the Worker code was deployed successfully.
3. If using a custom domain, ensure the DNS record for your Worker route is active.

This means you are sending faster than your provider allows. Every provider imposes a max sending rate (e.g. AWS SES defaults to 14 emails/second for new accounts).

To Fix: Go to Settings → Sending Rules → Rate Limiting and set your Max Emails Per Second to a value below your provider's limit. For AWS SES, you can view and request increases to your sending rate in the AWS SES Dashboard → Sending Limits.

Navigate to Audiences → Map Columns. Ensure you have a column explicitly mapped to the Email field. Vexifa requires at least one valid email column to create a campaign.

Encoding Issues: If your CSV contains international characters and imports garbled, save it from Excel as CSV UTF-8 (comma delimited) before importing.

This usually means the sending goroutines encountered a fatal provider error and stopped silently. Check the campaign's Send Log for error details (click the campaign → View Log).

Common causes:

1. Your provider API key expired or was revoked — verify credentials in Settings → Sending Providers.
2. Your AWS account hit its daily sending quota — check the SES Sending Statistics in the AWS Console.
3. The app window was closed mid-send — restart Vexifa and click Resume Campaign.

Vexifa receives bounce events through your Cloudflare Worker. Bounces are only processed if your sending provider is configured to forward notification events to your Worker URL.

For AWS SES:

1. In the AWS Console, go to SES → Verified Identities → (your domain) → Notifications.
2. Set the Bounce SNS Topic and Complaint SNS Topic to a new or existing SNS topic.
3. Subscribe that SNS topic to your Vexifa Cloudflare Worker URL via HTTPS subscription.

For other providers (Mailgun, SendGrid, Resend):

Go to your provider's dashboard → Webhooks. Add your Cloudflare Worker URL as the endpoint for Bounce and Complaint events.

A. Invalid API key: Go to Settings → Integrations and verify your OpenRouter key is correct and has not expired. You can test it at openrouter.ai/keys.

B. Insufficient credits: OpenRouter requires prepaid credits. Check your balance at openrouter.ai/credits. Free models (like google/gemini-flash-1.5 or meta-llama/llama-3.1-8b-instruct:free) cost $0 and do not require balance.

C. Model unavailable: Some models have rate limits on the free tier. Switch to an alternative model in Settings → Integrations → AI Model.

Check each of the following in order:

1. Sequence Status: Go to Automations and confirm the sequence shows Active (not Draft or Paused).
2. Trigger Conditions: Open the sequence and verify the trigger matches the actual event (e.g. "Tag Applied" won't fire if you're adding contacts via CSV import without applying the tag).
3. Frequency Cap: If global Frequency Capping is enabled and the contact recently received other emails, the sequence may be holding the send. Check Settings → Sending Rules → Frequency Capping or toggle the "Exempt from Cap" option on the sequence.
4. Contact Status: Open the contact record and check the Sequence History tab. If they already completed the sequence, they will not re-enter by default. Enable Allow Re-Entry on the sequence if needed.