System job steps versus custom job steps for scheduled tasks
Key Takeaway
Check the system job steps first, because they cover common tasks without code. When a job also needs an operation that no system job step provides, build a custom job step for that operation and keep the system job step for the common one.
A B2C Commerce job automates routine or long-running work, such as imports, exports, replication or search indexing. You can run a job manually or on a schedule. Job steps do the work inside a job, and they come in two kinds. System job steps are preconfigured and need no code. Custom job steps are steps a developer builds when no system job step does what the business needs.
Jobs, flows and steps
Every job contains at least one flow. Every flow contains at least one step. A flow controls the order in which its steps run. Each step tells the job what to do.
You can run a job manually, or schedule it to run at a specific time or on a recurring basis.
Each flow has a scope, which is one of these:
- The organization
- All storefront sites
- Specific sites
- Sites passed in at execution time through the OCAPI data API
Some system job steps, such as CreateSiteMap, run only in a site context. Data replication runs only in the organization context. A step placed in a flow whose scope it doesn't support shows an error.