Batches

An Apex Batch, or simply a Batch, is a mechanism that enables the processing of a large number of records by breaking the workload into smaller, manageable chunks.

The Action and Association Batch Processes execute logic within the managed package to perform critical tasks that keep your sequences moving forward.

Batch Responsibilities

The responsibility of the batch process and what it controls are:

• Checks if any participant meets their Sequence exit criteria
• Performs Automatic Email and SMS Actions via the Revenue.io API
• Sets Action Status to Initiated, and sets the Actual Execution Date
• Performs automatic skips for actions that do not meet action criteria
• Performs automatic skips for actions if a customer has opted out

Available Batches

The batches displayed on this page include:

• ActionProcessingBatch: Processes participant actions for all sequence record types.
• AssociationProcessingBatch: Processes sequence associations for all sequence record types.

Batch Owner

The Batch Owner is the running user who will execute the scheduled batch jobs. It is recommended that a System Administrator with a Guided Selling license click Set Batch Owner as this user will automatically be set as the batch owner. Setting the batch owner itself requires elevated permissions, and a batch owner with higher permissions also ensures all processes executed by the batch are successful since these include critical record updates.

Batch Schedule

Batches run at 30-minute intervals by default, and can be forced to execute or be skipped. If batches are still being processed at the time of the next job’s scheduled start, the next one will be aborted automatically. The interval can be adjusted as needed under Setup → Custom Settings → GS_Public_Settings → Sequence Schedule Interval

Disassociating Participants

Although participants are disassociated via triggers, there are instances where a participant (Lead or Contact) can be updated to meet a Sequence’s exit criteria without triggers running. One such scenario is when a non-sequence user updates a Lead or Contact. Since Sequence triggers don’t execute on non-Sequence user updates, the participant will not be exited from the Sequence in this case.

A batch process handles these cases by checking exit criteria during its scheduled runs.

Batch Interactions

The participant batch process interacts with the following components:

• Sequence Managed Package
• Revenue.io API

Monitoring Batches

You can monitor batch execution and status on the Batches page. More status details can be found by going to Setup → Apex Jobs. This helps you:

• Verify that batches are running on schedule
• Force batch execution when needed
• Skip batches if necessary for maintenance