Skip to main content

Diagnose Issues

Use this page when something in the WSO2 Integrator editor isn't behaving the way you expect: a feature doesn't respond, a diagram doesn't load, or an action errors out. Before you file an issue, capture verbose editor output so the team can act on the report.

If the editor shows WSO2 Integrator cannot start or Your project dependencies need to be updated after you move to Ballerina 2201.14.0, see Moving to Ballerina 2201.14.

Steps : Capture verbose editor output​

1. Enable verbose logging​

  1. Open Settings with Cmd+, on macOS, or Ctrl+, on Windows and Linux.

    Open Settings from the command menuOpen Settings from the command menu

  2. In the search box, type ballerina.

    Settings pageSettings page

  3. Set each of the following to the value shown:

    • ballerina.traceLog: enabled (true).
    • ballerina.debugLog: enabled (true).
    • ballerina-vscode.trace.server: verbose.

2. Open the output panel​

  1. Press Cmd+Shift+P on macOS, or Ctrl+Shift+P on Windows and Linux.

  2. Run Output: Focus on Output View.

  3. In the channel dropdown on the right of the Output panel, select Ballerina.

    Select the Ballerina output channelSelect the Ballerina output channel

3. Reproduce the issue and read the output​

  1. Repeat the steps that caused the unexpected behavior.
  2. Scroll through the Ballerina channel and look for errors or stack traces.
  3. Copy any error text you find.

Report the issue​

Open a new issue in the wso2/product-integrator repository and include:

  • A short title that describes the symptom.
  • The exact steps you followed to reproduce the issue.
  • The error text copied from the Ballerina output channel, in a fenced code block.
  • A screen recording of the reproduction, if you can capture one.

If the Ballerina channel doesn't show any error, still file the issue. Include the reproduction steps and the screen recording so the team can dig deeper from there.

What's next​

  • Moving to Ballerina 2201.14 - resolve the Ballerina version and dependency screens that appear after you move to Ballerina 2201.14.0.
  • Errors and stack traces - interpret the error text you captured from the Ballerina output channel.
  • Logging - add log statements once the editor is working again to trace what the integration does at runtime.
  • Debug Your Integration - set breakpoints and step through the integration after the editor issue is resolved.
Last updated on
On this page
Was this page helpful?
Report an issue