Troubleshooting

Go to Email Accounts and find the affected sender — it will show a Disconnected or Reconnect Required status. Outlook senders reconnect via a Microsoft OAuth flow; Gmail senders reconnect by re-entering their SMTP app password, since Gmail connects via SMTP, not OAuth, in Stynar. Any campaigns using that sender will resume automatically once reconnection is confirmed.

Gmail connects via SMTP + app password only — Google no longer grants the Gmail read scope to newly-connected OAuth senders, so a Gmail account can't gain native reply sync by reconnecting. Add IMAP details to that same SMTP sender in Email Accounts instead; once IMAP is added, lead replies appear directly in your Inbox rather than routing through a capture address.

Check that the SMTP host, port, username, and password are all correct. Many providers require an app-specific password rather than your regular account password — generate one from your provider's security settings. Confirm that port 465 (SSL) or 587 (STARTTLS) is open and not blocked by a firewall. Also verify that the SMTP user has permission to send emails as the From address configured.

Copy the DNS name and value exactly as shown in Stynar — extra spaces, incorrect capitalization, or missing characters will cause verification to fail. Check that the record was added to the correct DNS zone for the sending domain. DNS changes can take up to 48 hours to propagate globally; use the Verify button again after propagation completes.

All four setup steps must be fully completed before a campaign can launch — leads imported, email content configured, sender selected, and a schedule set. Check the campaign setup wizard for any steps marked as incomplete or showing a warning indicator. The Launch button remains disabled until every required field is filled.

Open the campaign — a banner at the top identifies the cause. Common reasons include insufficient credits, a revoked or disconnected sender account, reaching the monthly or daily email sending limit, or an AI usage limit. Resolve the issue shown in the banner and the campaign will resume automatically.

The daily sending cap is configured in the campaign's Schedule step. When the limit is reached, sending pauses until the following day. To increase throughput, raise the daily limit in the campaign scheduling settings or upgrade to a plan with a higher daily cap. For new sender accounts, keeping a daily limit in place helps gradually build sender reputation.

You have reached a limit on your current plan. Check the Billing page to identify which limit applies — campaigns, leads, mailboxes, or monthly email volume. Upgrade your subscription or purchase a credit top-up pack from the Billing page to restore access.

When credits run out, AI-personalized email generation stops and the campaign may pause. Purchase a credit top-up pack from the Billing page — Small, Medium, Large, and XL packs are available and apply to your balance immediately. Once credits are restored, the campaign resumes automatically.

Confirm that the {{AI_CONTENT}} variable is present in your template at the position where personalized content should appear, and that your credit balance is sufficient — AI generation is skipped when credits are depleted. Review your remaining credit balance on the Billing page.

Open Campaign Analytics and review the follow-up sequence for the affected campaign. Common causes include: the lead already replied (which stops the sequence), a delay hasn't elapsed yet, or the campaign is paused due to a credit or plan limit. Confirm that all sequence steps have the correct trigger conditions, delays, and actions configured.

Auto AI Reply requires the AI Classify Reply step to first detect the intent of the incoming reply. Confirm the campaign's follow-up sequence includes an AI classify step before the auto-reply action. Check the lead's conversation in the Inbox to see the classified intent — replies classified as Not Interested or Unsubscribed will not trigger an auto-reply.

Leads missing an email address or first name cannot be imported — these fields are required. Fix missing values directly in the review table before confirming, or delete those rows. Duplicate email addresses are also auto-skipped, with only the first occurrence imported. Look for red indicators in the review table to identify all affected rows.

Confirm the file has clear column headers in the first row and that an email column is present and correctly labelled. Remove any duplicate column names before uploading. During import, verify the column mapping step and reassign any columns mapped to the wrong lead fields before confirming.

Confirm you are authenticating with the correct CRM account that has access to the contacts you want to import. HubSpot, Pipedrive, and Zoho are all connectable today — each requires specific API access scopes, so verify your CRM account has the necessary contact export permissions enabled. For HubSpot or Zoho, disconnect and reconnect from Settings → Integrations; for Pipedrive, reconnect from wherever you're importing leads — Saved Lists or a campaign's Leads step.

Variable names in templates must exactly match the column header mapped during lead import — including capitalization. If the template uses {{firstName}}, the imported column must also be mapped as firstName.

Any sender without reply sync routes replies to a capture address instead of the platform Inbox, and shows a warning badge in Email Accounts. The fix depends on the sender type: Gmail senders need IMAP details added (Gmail is SMTP-only, so OAuth reconnect doesn't grant it); Outlook senders just need to reconnect and approve the Outlook mail-read permission; SMTP senders need IMAP host/port/credentials added the same way as Gmail.

Go to the Meetings page and click Connect Google Calendar. Sign in with the Google account you want to use for availability checking and approve all requested permissions — including calendar read and event creation scopes. If the connection fails, try revoking Stynar's access in your Google account security settings and reconnecting from scratch.

The AI must detect scheduling intent in the lead's reply to trigger the booking flow — vague or ambiguous replies may not be detected. Check the lead's conversation in the Inbox to see whether intent was classified. Also confirm that Google Calendar is connected on the Meetings page and that the campaign's follow-up sequence includes a meeting booking step.

A Booking Failed status means the calendar event could not be created — most often due to a missing or expired calendar permission. Go to the Meetings page, reconnect your Google Calendar, and ensure all calendar scopes are approved. If the issue persists, verify that the connected Google Calendar is active and accessible from your Google account.

Open tracking works via a small pixel embedded in HTML emails. If recipients have image loading disabled in their email client, opens will not be recorded even when the email is read. Plain-text emails do not support open tracking at all. Check the Sent On and delivery status columns in Campaign Leads to confirm emails were delivered rather than failed or bounced.

Verify that all DNS authentication records (SPF, DKIM, DMARC) are correctly set and passing validation. Reduce your daily sending volume or enable the gradual send ramp-up for new senders. Clean your lead list by removing invalid addresses, opt-outs, and disengaged contacts. Avoid misleading subject lines or promotional language, and monitor your domain reputation in Google Postmaster Tools.