Jobs

👍

Welcome note

Data hub is our new upgraded platform, which we rolled out in August 2025. It offers a single unified integration for passing your data through to your Bloomreach products.

You have access to Data hub if you've implemented with Bloomreach after August 2025.

Customers who have implemented before August 2025 should follow the existing documentation for Engagement, Discovery, and Clarity.

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.

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.

Job types

Records update jobs

Created 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.

Configuration update jobs 

Created whenever the item collection configuration is updated.

Items update jobs

Created when the system 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

Created when items sync to connected destinations (Engagement or Discovery). These jobs run automatically when you enable a destination or when item data changes. These jobs track how many items were sent to each destination.

Import jobs

Created when scheduled or manual imports run to bring data from external sources into your collection. These jobs show the import execution status and any data processing that occurred.

Viewing jobs

Review the detailed guide on viewing jobs.

Next steps

Now that you understand jobs:

• Set up destinations to send items to Bloomreach products.