The issue described is a mismatch between the code version directory where the developer is uploading files and the code version that is currently active on the B2C Commerce instance. Cartridges are uploaded to a specific version directory (the "target version"). However, the instance only executes the code from the single version designated as "active" in Business Manager. By changing the server connection's target version directory in the development environment to match the name of the currently active code version, the developer ensures that their uploaded files overwrite the code that is actually running, thus solving the problem.

1. Salesforce Help

B2C Commerce

Manage Code Versions: "You can have multiple code versions on an instance

but only one is active at a time. The active version is the code that is currently running on the instance." This establishes the core principle that only the active version executes.

2. Trailhead

Salesforce B2C Commerce for Developers

Set Up Your Local Workspace: This module details the creation of the dw.json configuration file for server connections. The code-version property within this file specifies the target directory for code uploads. The scenario implies the developer's code-version is different from the active version on the server.

3. Trailhead

Salesforce B2C Commerce for Developers

Deploy Your Code: This module explains the two-step process: uploading code to a version directory and then activating that version in Business Manager (Administration > Site Development > Code Deployment). The problem occurs when the first step is done but the uploaded version is not the active one. Option D provides a developer-side solution to this misalignment.