What are all these APEX jobs that Message is running?

This article is intended for Salesforce Admins

Both of Message's Salesforce packages have a number of jobs that run. Which jobs run depend on your particular settings, but below is the full list and along with a brief description. If you have more detailed questions about how Message works with Salesforce, reach out to our support team.

Data syncing jobs

These jobs handle the complex process of syncing data between Message and Salesforce. It includes maintaining the record index, managing conflicts, creating logs and cleaning up as needed.

SV_ConflictFieldBatch
This job syncs over data when a bi-directional conflict has been resolved by a user. This job is only used if you have bi-directional fields mapped.

SV_ImportParticipantBatch
This job checks for indexes any record in Signal Vine that has a valid Salesforce ID and has not yet been indexed. To avoid monopolizing resources, it only checks Signal Vine records that have changed since the last sync.

SV_ParticipantCheckBatch
This job checks that indexed records still exist in Salesforce.

SV_ParticipantCheckSVBatch
This job checks that indexed records still exist in Signal Vine.

SV_SVSyncObjectBatch
This job updates the sync index when a record in Signal Vine has opted out.

SV_ExportMulitpleContactBatch
This job syncs data between Salesforce and Signal Vine. It goes through each record in the queue and syncs data based on your field mapping. Each batch will process 50 records. 

SV_ExportParticipantBatch
This job adds new records to Signal Vine when Process Builder is set up to send new records over. Each batch will process 50 records.

SV_CheckLogBatch
This job checks Signal Vine for the results of the data sync.

SV_deleteTriggerBatch
The job will remove items from the sync queue once they've been processed.

SV_ImportInactiveParticipantBatch
- This batch job will sync the inactive participant records
- No dependency batch job

SV_SyncLogCleanupSOQLBatch
This job will delete old sync log entries based on the timeframe you've set for retention. The timeframe is customizable.

SV_ProgramTriggerBatch
This job will ensure that sync triggers exist for all mapped objects for each program.

Messaging jobs

SV_PermissionBatch
This job ensures that permission sets are updated when a program's user permissions are changed. This job only runs if the user assigning the permissions doesn't have direct access rights to update the permission set.