The B2C Sync panel shows what goes to your instances. It has a tab for each instance that a deployment or upload went to. Each instance has a Code Deployment tab for its latest deployment and a Code Upload tab for the files sent to it, with a console that prints the instance's sync output
Open the panel
The panel is the B2C Sync tab in VS Code's bottom panel. Like any view, you can drag it to a side bar. It opens from:
- Intellij SFCC: Show B2C Sync in the Command Palette
- A deployment's status bar item, such as Sandbox 01: 🚀 Uploading cartridges 2/4, which opens that instance's Code Deployment tab
- The upload item next to the auto upload toggle. After a single file, it opens the Code Upload tab on that file's uploads
- See details in the notification that ends a deployment, and Show in B2C Sync in an upload notification
- A deployment you start. The panel switches to that instance's Code Deployment tab, so the last one started is the one you see
A short panel opened this way grows until its table shows eight rows, never past half the screen. Docked at a side, it keeps its size. In either tab, Cmd+F (Ctrl+F on Windows and Linux) moves to the filter field, or opens the console's find when the console is alone in sight. Where the status shows lists the signs in the editor tab, the Explorer, the saved line, and the status bar that lead here
Instance tabs
Each tab names its connection and shows the hostname on hover. The active connection has the connected cloud icon. A green dot on a tab's icon means a deployment or upload runs on that instance. A red dot means the latest deployment failed or a file's latest upload failed, and it clears once that file goes up or leaves the history
The Code Deployment and Code Upload tabs below carry the same dots for their own work, with the tooltips Running and Has failures. Each instance remembers which of the two was open. An upload you start switches its instance to Code Upload, unless a deployment runs there
Layout and console
The last three toolbar buttons are the same on both tabs:
| Button | What it does |
|---|---|
| Console | Picks the layout: Hide Console, Show Console Beside, or Show Console Only. The choice applies to every instance and window. Drag the line between the table and the console to resize them |
| Open in Output | Opens the B2C Sync Log output channel, which has the lines of every instance |
| Clear Console | Empties this instance's console |
The console shows the instance's lines, newest at the bottom, and follows new lines while you are at the end. Scroll up to read, and Scroll to the Newest Line takes you back down. A line that belongs to no instance, such as 🙉 File Watcher Started, goes to the active connection's tab. B2C Sync panel and log explains each line
Cmd+F (Ctrl+F on Windows and Linux) in the console opens Find in Console. It highlights every match, starts at the newest, and counts them, such as 2 of 5. Enter and Shift+Enter, or the arrows, move between matches, and Esc closes it
The path of an uploaded file in a line is a link, also inside a WebDAV URL. Click it to open the file, or to select a folder in the Explorer
Status line
Under the tabs, a status line says what runs, where it goes, and how it went. The code version and the hostname in it are links that show them in B2C Explorer
At the end of the line, Parallel requests: 7 opens a menu of 1 to 8, 10, 12, 15, and 20. It sets how many requests deployments send to each instance at once, and how many saves go up at a time. A running deployment takes the new value for its next requests. It is the same value as the intellij-sfcc.concurrentRequestsPerSecond setting
Code Deployment
This tab shows the latest deployment to the instance, cartridge by cartridge. Until there is one, it reads No deployments yet, with a Deploy Code… link that opens the Deployment Manager
Status and progress
While a deployment runs, the status line reads Deploying to version3, then the hostname and the stage: Zipping 2 of 4, Connecting, Removing old cartridges 1 of 3, and then 2 of 4 done with the bytes sent, such as 1.6 MB of 2.5 MB. The time runs at the end, and failures show in red as they happen. Click the red count, such as 1 failed, to show only the failed cartridges
When it ends, the line reads one of these, followed by the code version, the hostname, the total size, and the time:
| Status line | Meaning |
|---|---|
| Deployed 4 cartridges in 0:12 | Every cartridge deployed |
| 3 deployed, 1 failed in 0:14 | Some cartridges failed or were skipped |
| Stopped after 0:05: 1 of 4 deployed | You clicked Stop Deployment |
| Deployment failed after 0:02 | Nothing went up. The reason follows, such as The sandbox is stopped, Cannot connect, the instance answered 503, or Cannot reach the instance |
In a finished line, 1 failed is a link too. It clears the filter field and selects the Failed pill
When old cartridges could not be removed before the upload, the line adds a warning such as 1 old cartridge could not be removed, with the names on hover
Below the status line, a strip shows each cartridge as a segment as wide as its zip. A segment is blue while its cartridge uploads or unzips, green once deployed, and red when it failed. It stays empty while the cartridge waits or after it was skipped. Hover a segment for its cartridge, status, and size, and click it to select its row
Deployment toolbar
| Button | What it does |
|---|---|
| Deploy Code… | Opens the Deployment Manager. Shown until the first deployment |
| Deploy Again | Deploys the same cartridges to the same instance and code version once more |
| Retry Failed and Skipped | Deploys only the cartridges that failed or were skipped |
| Stop Deployment | Stops the running deployment. The cartridges that had not finished become Skipped. The console adds ⏹ Deployment stopped: 1 of 4 deployed, and a notification says Deployment to Sandbox 01 stopped: 1 of 4 deployed, with See details |
Deploy Again and Retry Failed and Skipped wait until the running deployment ends
Filter the cartridges
The pills All, Running, Queued, Done, and Failed show their counts, and Skipped joins them when a deployment ended early. Filter cartridges matches cartridge names, and Esc clears it. When nothing matches, Show all brings every row back
Deployment columns
| Column | Shows |
|---|---|
| Cartridge | The name, with the icon of a cartridge, a B2C module, or the global modules folder. Hover for the kind and the path |
| Status | The state, with its icon |
| Progress | A bar while the cartridge uploads or unzips |
| Size | The zip size, or 1.6 MB of 1.9 MB while it uploads |
| Time | How long the cartridge took |
Click a header to sort by it, click again to reverse, and a third time to restore the order. In a narrow panel, Time hides first, then Progress
| Status | Meaning |
|---|---|
| Queued | Waits for a free request |
| Removing old copy | The cartridge's old copy is deleted from the code version |
| Uploading 64% | The zip goes up |
| Waiting for the instance | The zip is sent, and the instance has not answered yet |
| Unzipping | The instance unzips it |
| Cleaning up | The zip is removed from the code version |
| Deployed | Done. Deployed, zip left in the code version and Deployed, old copy not removed add a warning |
| Failed | It failed, with the reason: Upload failed: …, Unzip failed: …, 401 Unauthorized, check the credentials, or 521 Sandbox is stopped |
| Skipped | The deployment ended before the cartridge finished |
Deployment rows
Select rows with a click, a Shift or Cmd click, the arrow keys, or Cmd+A (Ctrl on Windows and Linux). Enter or a double click runs Show in Console: the console opens beside the table, without changing your layout, and scrolls to the last line that names the cartridge. Cmd+C copies the selected rows. The context menu has:
- Show in Console
- Reveal in Explorer View, which selects the cartridge folder in the Explorer
- Copy
- Deploy Selected Again, which deploys only the selected cartridges
Code Upload
This tab lists the files sent to the instance: the saves that auto upload sent and the files you upload. The history is kept per workspace, 30 days by default, so it is still there after a restart. Until the first upload, the tab reads No uploads yet
Upload status line
The line starts with what uploads do now:
- Uploading 2 files while uploads run
- Auto upload is on or Auto upload is off on the active connection's tab
- Not the active connection on any other tab, since auto upload only sends to the active connection
The code version and hostname links follow, then the number of uploads, such as 12 uploads, the failures in red, such as 1 failed, and how long the history is kept, such as kept 30 days
The failures count only the files whose latest upload failed. When a file goes up again, even while that upload still runs, its older failure leaves the count, the Failed pill, and Retry Failed Uploads. The failed row stays in the history under All
Click the red count to see the failures left. It selects the Failed pill, clears the filter field and the file chip, and resets Source and Period when they hide one of the failures
Upload toolbar
| Button | What it does |
|---|---|
| Upload Again | Sends the selected files once more, each file once however many of its rows are selected |
| Retry Failed Uploads | Sends each file whose latest upload failed once more |
| Stop Uploads | Stops the running uploads, or only the selected ones, as Stop 2 Uploads |
| Auto Upload | Turns auto upload on or off for the active connection, like the status bar toggle. It looks pressed while on |
| Filter Uploads | Opens the filter menu. A blue dot marks it while it hides rows |
| Keep History | Keeps uploads for 1 day, 7 days, 30 days, or 90 days |
| Clear History | Asks Remove 12 uploads from the history? Uploads that still run stay, and clears the history on Clear |
Upload Again and Retry Failed Uploads send the files as a manual upload. A notification shows Sandbox 01: Zipping 0/1 and then Uploading 1/1, and ends with Uploaded Checkout.js to Sandbox 01. The new rows have Manual as their source
Filter the uploads
Filter Uploads has these choices, kept for every instance and window:
| Choice | What it does |
|---|---|
| Latest Upload of Each File | On by default. One row per file, its newest upload, with ×3 after the name when the file went up three times |
| Any Source, Uploaded on Save, Uploaded by Hand | Shows every upload, only auto uploads, or only manual ones |
| Any Time, Today, Last 7 Days | Limits the period |
| Reset Filters | Restores the defaults |
Running uploads always show. The pills show their counts. All is always there, and Running, Uploaded, Removed, and Failed show while they have rows or are selected. Filter files matches the file's path in its cartridge. Failed lists only the failures no later upload of the file settled
Upload columns
| Column | Shows |
|---|---|
| File | The file's icon and name, its folder in the cartridge, and its cartridge on the right. Hover for the local path |
| Status | The state, with its icon |
| Source | Auto for a save, Manual for an upload you started |
| Size | The file size, or 4.1 kB of 6.3 kB while it uploads |
| Took | How long the upload took |
| When | When it started. Hover for the full date |
The newest uploads come first, and running ones stay on top whatever the sort. In a narrow panel, Source hides first, then When
| Status | Meaning |
|---|---|
| Uploading 64% | The file goes up |
| Waiting for the instance | The file is sent, and the instance has not answered yet |
| Removing | A deleted file is being removed from the instance |
| Created or Updated | The file was new on the instance, or replaced the one there |
| Uploaded | The file went up |
| Uploaded and unzipped | A folder went up as a zip and was unzipped |
| Removed | A deleted file was removed from the instance |
| The reason | The upload failed. The row turns red and shows why, such as the HTTP code, Stopped, or Ended without an answer |
Upload rows
Enter or a double click opens the file in the editor, or selects a folder in the Explorer. For a removed file, it runs Show in Console. Cmd+C (Ctrl+C on Windows and Linux) copies the selected rows, and Delete removes the finished ones from the history. The context menu has:
- Upload Again
- Stop Upload, for a running upload
- Open in Editor, for every selected file
- Compare with Instance, which opens a diff of the local file and its copy in the active code version. Only the active connection's tab offers it
- Reveal in Explorer View
- Show Uploads of This File, which lists only that file's uploads. A chip with the file name shows next to the pills, and its × lists every file again
- Show in Console, which opens the console beside the table, without changing your layout, and scrolls to the last line that names the file
- Copy
- Remove from History, for finished uploads
The upload status bar item and Show in B2C Sync open the tab the same way, on the uploads of one file