Jobs

This guide introduces you to the concept of jobs. 

What are jobs

Jobs are asynchronous operations that run in the background whenever you perform major actions in an item collection. Jobs run when you: 

• Update records.

• Reprocess items after schema changes.

• Import data from external sources.

• Create and modify destinations.

Jobs automate efficient, reliable, and scalable management of data and configurations across Bloomreach products. Each item type in a collection generates its own jobs. Actions on one item type never affect jobs for another item type in the same collection.

Why are jobs important

Jobs let you track your system's big operations and provide visibility into data processing that happens asynchronously in the background. If something goes wrong or you want to confirm everything is done, the Jobs are your first stop.

Job information

Each job provides specific information about its execution:

• States: Whether the job is Pending, Running, Success, Fail, or Canceled.

• Timed execution: How long a job took and any queue time if the system is busy.

• Errors and warnings: Details about any issues encountered during execution.

• Job ID: Unique identifier for the job, useful for debugging.

• Initiator: Who or what triggered the job: Job for a system-triggered follow-on job, or the email of the person who made the change.

Job types

Records update jobs

Data hub creates this job when you ingest data via API or with Imports. These jobs show how many records were added, updated, or processed during the operation.

After data ingestion, check the jobs tab to find the Records update job. If the job succeeds, it shows record counts. If it fails or shows warnings, check the error details in the job information.

Records update jobs for API requests also process override data. Job details don't list separate counts for it, and jobs don't warn about override data that doesn't match a context. After you send override data, check your records and items.

Configuration update jobs 

Data hub creates this job when you update an item type's configuration, such as its schema, identifier settings, or destinations.

Items update jobs

Data hub creates this job when it transforms records into items based on your schema configuration. These jobs run automatically after schema changes or when triggered by record updates with specific parameters.

Destination items update jobs

Data hub creates this job when items sync to the item type's connected destinations (Marketing or Search). In the Data hub interface, this job starts automatically after you save a change. For API updates, you choose whether a successful job starts the next one. To configure this, see Automatic success triggers. These jobs track how many items were sent to each destination.

Import jobs

Data hub creates this job when scheduled or manual imports bring data from external sources into the item type's records. These jobs show the import execution status and any data processing that occurred.

View jobs

Review the detailed guide on viewing jobs.

Next steps

Now that you understand jobs:

• Set up destinations to send items to Bloomreach products.