Capella Troubleshooting
My Capella crashed. What should I do?
Capella can crash for many different reasons. Many issues are issues with Eclipse Capella itself, so we try to escalate issues there. Bugs can be reported to the Eclipse Capella team directly in the Github repository.
Global administrators can see the logs of all sessions to identify the issues remotely. In addition, the session owner can also see the events in the UI. In your session, please follow these steps:
- Open the Capella search via the search icon.
- Search for
Event Logs (General)
and open the view. - You should now see the list of events and you can try to find an entry with a matching timestamp.
The description editor doesn't load anymore
In some cases the description doesn't load anymore, is just a blank page, or looks like this:
This is a common and known bug in Capella itself. We have reported it to the Capella contributors, but the bug originates in the Eclipse/Nebula framework. The bug was fixed in Eclipse version 4.24. Capella 6.0.0 and 6.1.0 are based on Eclipse 4.20, so the bug is still present in these versions. Capella 7.0.0 is based on Eclipse 4.27 and the description editor issues are fixed.
If you are experiencing this problem, please try one of the following workarounds:
-
Use the "Semantic" or "Expert" view in Capella to modify the description. To do so, open the properties tab of the element you want to edit and click on the "Semantic" or "Expert" tab. In this editor, rich text is not supported! You have to enter valid HTML. The content is not validated and may later impact other components of the toolchain if invalid.
-
Open the description editor by double-clicking the model element you want to edit, and open the description editor from the overlay:
- Open the Description Editor from the Properties tab:
-
Reopen Capella in the current session from the task bar at the top of the session window. Expand
File
and close Capella. It will reopen automatically. -
End your session and request a new session in the Capella Collaboration Manager.
If none of these workarounds help, the only solution is to reset your workspace. Please contact your administrator for assistance.
My Capella is slow. What can I do?
A slow Capella instance can have multiple reasons. Here are some common issues:
-
Disable the automatic refresh in the Semantic Browser
The automatic refresh of the Semantic Browser slows down Capella when connected to a TeamForCapella repository.
By default, the Semantic Browser auto-refresh is enabled. You can disable it in each session using the button marked in the screenshot (red/right box). After you've disabled the auto-refresh, you can manually refresh the Semantic Browser by clicking the refresh button (blue/left box):
When you want to save the option for all future sessions, disable it in the UI first and then close Capella to save the workbench state:
-
Close all unrelated projects and tabs
Navigate to the project explorer in Capella and right-click the project you want to work on. Select "Close projects":
Then, confirm the dialog:
This will close all projects except the selected one.
If none of those steps help, please reach out to your system administrator.