SequenceEnrollmentBlock

Why one contact could not be enrolled.

type SequenceEnrollmentBlock {
  contact_id: ID!
  contact: Contact
  workflow_id: ID
  workflow_name: String
  is_sequence: Boolean!
  already_in_this_sequence: Boolean!
  is_deleted: Boolean!
}

Fields

SequenceEnrollmentBlock.contact_id ● ID! non-null scalar

SequenceEnrollmentBlock.contact ● Contact object

Resolved so the UI can name the contact rather than showing its id.

SequenceEnrollmentBlock.workflow_id ● ID scalar

The automation already holding this contact. Null when the blocker is this sequence itself.

SequenceEnrollmentBlock.workflow_name ● String scalar

SequenceEnrollmentBlock.is_sequence ● Boolean! non-null scalar

Whether the blocker is another Sequence rather than a marketing workflow.

SequenceEnrollmentBlock.already_in_this_sequence ● Boolean! non-null scalar

The contact is already in THIS sequence. A distinct case from being held by another automation, and the one a rep hits most often when re-adding a list.

SequenceEnrollmentBlock.is_deleted ● Boolean! non-null scalar

The contact is deleted. Enrollment writes its rows in raw SQL and so does not see the soft-delete scope, but materialisation reads through Eloquent and does — a deleted contact would enrol and then never produce a task.

Member Of

SequenceEnrollmentResult object