The JetBrains plugin can pause a running SFCC pipeline at supported nodes and show its execution context in the IDE. Use it to investigate legacy pipeline behavior alongside the visual Pipeline Editor.
Prepare the session
Follow Debugger setup to select the development connection, enable debugging on the sandbox, and create a Salesforce B2C Commerce (SFCC) debug configuration. Upload the pipeline version you intend to debug and keep the corresponding cartridges open locally.
Set a pipeline breakpoint
Open the pipeline XML in the visual Pipeline Editor and add a breakpoint at a supported pipeline node. Pipeline breakpoints are identified as SFCC Pipeline in the IDE's breakpoint controls. Breakpoint placement depends on the node and source location; arbitrary XML lines are not all executable positions.
Start the selected debug configuration, then trigger the storefront request that runs this pipeline on the active sandbox. When the breakpoint is reached, inspect the current pipeline frame and node before continuing.
Step through execution
Use the debug controls to resume execution, step over, step into, or step out as appropriate for the selected frame. Follow the pipeline call stack to understand how execution reached the current node.
The visual editor and XML source are complementary views. Use Show Pipeline Editor or Show Pipeline Source to switch when you need the graph or its underlying XML.
Inspect the Pipeline Dictionary
Expand Pipeline Dictionary in the variables view to inspect values for the paused pipeline frame. Expand available members and evaluate expressions in the selected debugging context when investigating a value or branch condition.
Dictionary contents reflect the current suspended execution. Select the relevant stack frame before comparing values from different parts of a call chain.
Troubleshoot missed breakpoints
- Confirm that the request reaches the intended pipeline and node.
- Verify the selected sandbox, code version, site, and cartridge order.
- Upload the current local pipeline source and check that the breakpoint is on a supported node.
- Check the debugger connection and disconnect another debug client if it is already using the sandbox session.
For JavaScript controllers, hooks, and scripts, use the script debugging guide. For graph editing and the embedded editor's runtime requirements, see Pipeline Editor.