Skip to content

Batch Processes

Role:
Administrator

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 Sequence Participant Batch Process is logic that executes within the managed package to:

  1. Execute automatic actions associated with a sequence
  2. Flag subsequent actions to be shown on the Today view (Engage)
  3. Disassociate participants from a Sequence if some update caused them to meet their related Sequence’s exit criteria

Available Batches

The batches displayed on the Settings page include:

  • Campaign Batch: Processes participant actions for Campaign Members
  • Contact Batch: Processes actions related to Contacts
  • Lead Batch: Handles actions for Leads
  • Opportunity Batch: Processes participant actions for Opportunity Contact Roles

Batch Schedule

Batches run at 30-minute intervals and can be forced to execute or be skipped. Additionally, they assist in processing any orphaned actions that may have been misprocessed during regular operations.

Batch Responsibilities

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

  • Checks if any participant meets their Sequence exit criteria
  • Performs Automatic Native Email Actions via the Revenue.io API
  • Sets the “Is_Initiated”, “Actual_Execution_Date” values on the participant Action
  • Performs automatic skips for actions that do not meet action criteria
  • Performs automatic skips for actions if a customer has opted out
  • Sets the “Show on Today” field of subsequent Participant Actions

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. This helps you:

  • Verify that batches are running on schedule
  • Identify any batch failures
  • Force batch execution when needed
  • Skip batches if necessary for maintenance
If batches encounter failures, it may be necessary to get support from Revenue.io to resolve the issue.

Best Practices

  • Monitor batch execution regularly
  • Review batch logs for errors
  • Force batch execution when needed for troubleshooting
  • Understand batch timing and schedule
  • Coordinate batch operations with other system processes
Last updated on