Troubleshooting
VS Code editor focus
If the editor window is not in focus, the watsonx Code Assistant™ for Z menu item might not show up.
Solution: Left-click in the file that you want an explanation for before you click right.
VS Code noneditor focus
When a noneditor window (like a WebView) is opened, right-clicking within the window can shift the focus to the noneditor window, which can make explanation behave in unexpected ways
Solution: Close any noneditor windows before trying to generate explanations.
VS Code open editor with selection
When the name hyperlink is clicked; sometimes after the file opens, the selection will be made and will disappear immediately.
Solution: Try to click the name hyperlink again.
LLM context window
There is a limit to the amount of input that the large language model (LLM) can take in at one time.
Solution: Generate multiple smaller explanations instead of one large one.
Large COBOL program summaries
Depending on the size and structure of the COBOL program, the background task generating the explanation may end with an error message stating that the number of input tokens cannot exceed the total tokens limit for the model. If this message is encountered, the explanation cannot be generated for this entire program at one time.
Solution: Either generate explanations at the paragraph level or open a support case with IBM® for further investigation.
CICS handle conditions
Large program explanations for files that contain CICS® handle conditions are not always complete.
Solution: Generate explanations at the paragraph level for programs that do not contain CICS handle condition statements.
Known limitations - Large Program Explanation in chat
- The user interface does not automatically focus on the correct chat session.
When the final summary is generated, the user interface does not automatically focus on the correct chat session. Manually identify and switch to the correct session.
- Loader state is chat wide, not session specific.
The loading indicator applies to the entire chat interface rather than individual sessions. Switching between sessions during processing might cause the loader to reset, even if the operation is still in progress.
- Buttons remain active after being clicked.
Users can unintentionally trigger the explanation process multiple times by repeatedly clicking the button. This might result in performance issues or inconsistent outputs.