b2c-job_skill

Overview

This skill runs and monitors existing Salesforce B2C Commerce (Demandware/SFCC) jobs using the b2c CLI and handles import/export of site archives (IMPEX). It focuses on executing batch/system jobs, checking status, viewing logs, and moving site data between local and instance storage. Use this for operational tasks; for authoring new job step code use the custom-job-steps skill.

How this skill works

The skill invokes the b2c CLI commands to run jobs, optionally waiting for completion, passing parameters, or supplying raw JSON request bodies for system jobs. It uses the job import/export commands to push or pull IMPEX site archives and provides helpers to search executions, wait on execution IDs, and show logs when failures occur. If the b2c CLI is not globally installed, it supports running via npx.

When to use it

• Run an existing batch job or system job (e.g., search indexing).
• Import a local site archive directory or zip into a B2C instance.
• Export site data from an instance to create an archive.
• Check job execution status, search job history, and retrieve logs on failures.
• Wait programmatically for job completion before continuing a deployment or pipeline.

Best practices

• Use --wait and --timeout for long-running jobs to avoid orphaned executions.
• Provide parameters with -P for standard jobs; use --body only for jobs that require raw JSON (they are mutually exclusive).
• Use --show-log when runs fail to capture error details for troubleshooting.
• Keep archives on the instance only when necessary (use --keep-archive sparingly).
• Run the CLI via npx if the global b2c plugin is not installed to ensure consistent tooling version.

Example use cases

• Run a nightly product indexing job and wait for completion before switching search traffic.
• Import storefront content from a local export prior to a functional test run in a sandbox.
• Export an instance archive to capture current site data before a major deployment.
• Search recent job executions to diagnose intermittent failures and view their logs.
• Trigger a system job (search index) with a custom site_scope JSON body for targeted reindexing.