Skip to main content
Each entry lists the symptom, the most likely causes in order, and where to look. Every enrollment has an event timeline (open the person in the sequence’s people list); it answers most questions faster than any setting.

​
Emails are not sending

A sequence sends only while enabled. Open it and check the toggle. Enable is refused when there are no steps, or when an email step exists and no mailbox is available to the sequence.
Emails send from the enrollment owner’s assigned mailbox, or from the shared pool if they have none. If the owner has no assignment and the pool is empty, nothing can send. Check Mailboxes › Belongs to and the pool.
Automatic emails only go out inside the sequence’s days and hours, in the prospect’s timezone when known. A step due at 6 PM Friday sends Monday morning. Check the enrollment’s next step due time.
A mailbox that reached its daily limit waits for tomorrow. A mailbox that is disabled or suspended does not send at all. Open the mailbox to check both.
A paused enrollment does not send. The pause reason is on the enrollment: rep paused, reply action, rule, or sequence disabled. A pending enrollment is either awaiting approval or waiting for the sequence to be enabled.
The default policy skips email steps after three unopened emails. The timeline shows step skipped with the rule name.
Sends may go out but land in spam. Open the mailbox’s DNS check and fix SPF, DKIM or DMARC.

​
People were refused at enrollment

The preview and the sequence’s enrollment attempts list show the reason for every refusal. If far fewer people enrolled than expected from a CRM list, check the list scope: my contacts is CRM ownership, my call queue is the CRM task queue. They are different sets.

​
An enrollment is stuck

A rule held it for approval. A manager approves or rejects it from the people list under Awaiting approval.
Enabling the sequence resumes exactly the enrollments that disable paused. Enrollments a rep paused by hand stay paused and need a manual resume.
The next step date is rolled into the sending window. If the sequence’s schedule has no open days, nothing ever becomes due. Check days of week and hours.
The failure reason is on the enrollment: usually a mailbox that was deleted or lost its connection. Fix the mailbox, then use Retry on the enrollment.
A manual step is a task. If it stays open, the step’s auto-skip delay eventually expires it and the enrollment moves on. If there is no auto-skip, it waits until someone acts.

​
Tasks

Held tasks are hidden while the enrollment is paused and return when it resumes. Cancelled tasks are gone for good because the enrollment ended (reply, bounce, unsubscribe, rep finished it). Check the task’s state in its activity timeline.
Click Open call list on the tasks page; it rebuilds the system dial list from the open call tasks. Completing a call to the person from any list also completes the task.
Expiry comes from the step’s auto-skip delay. Lengthen or remove it on the step. Snoozing a task moves the deadline with it, so snooze rather than leave a task overdue.
Reassigning a sequence task reassigns the whole enrollment; later sends come from the new owner’s mailbox. If the new owner has no mailbox and the pool is empty, sends wait.

​
Mailboxes and Google

The Workspace has not trusted the Salesfinity app. A Google Workspace admin must add it as a trusted app in the Admin console, then the mailbox owner connects again. This is a one-time change per Workspace.
Google only issues a refresh token on the first authorisation. Disconnect the mailbox fully and connect it again so a new refresh token is stored.
Use an app password rather than the account password, confirm host and port (SMTP 587 or 465, IMAP 993 for most providers), and check that IMAP is enabled on the account. The provider’s error text is shown in the connect dialog.
Open the DNS check. No SPF, two SPF records, or a permissive +all are critical; a missing DMARC or a weak SPF qualifier is needs-work. The check names the record and the fix.
Rejected rows show the provider error. Duplicate means the address is already connected on the team; nothing was changed for it.

​
Replies

Replies are matched by thread. If the prospect replied to a different email, or forwarded, the reply may have been classified as unknown, in which case the sequence’s reply action applies (finish by default). The timeline shows the category and confidence.
Check, in order: auto-send enabled; the reply’s category is selected; the category is not one of the banned five (unsubscribe, out of office, auto-reply, wrong person, unknown); the confidence is above the minimum; the daily cap is not reached; and, if respect schedule is on, the sending window is open.
Unsubscribe replies are classified and suppress the email automatically. If the reply was ambiguous (“please stop” without the word), it may have landed as not interested. Add the address to suppression by hand.

​
Two reps emailed the same account

The default policy warns, but does not block, when another rep is already working a contact, and stops everyone else at a company only after a meeting or a positive reply. To block on contact, change the active in another sequence scenario to Do not enroll, and consider a touched within the last N days scenario at the account level.