Troubleshooting

This page provides solutions for the most common Kotar problems.

Problem	Possible Cause / Resolution
Workspace cannot be opened	Verify that the browser has permission to access the selected directory. Reopen the workspace and grant file-system access when prompted.
Previously opened workspace is no longer accessible	Browser permissions may have been reset or revoked. Open the workspace again and grant access to the directory.
Changes made by another application are not visible	Refresh or reopen the affected file/workspace. Automatic detection of external changes may depend on the browser and Kotar version.
SysML file shows errors	Check the Problems/Diagnostics view for syntax, semantic, validation, or lint findings. Fix syntax errors first, as they may cause additional semantic errors.
Graphical view does not match the text	Make sure the textual model is syntactically and semantically valid. Invalid or incomplete text may prevent the graphical projection from being updated correctly.
Diagram layout changed after editing text	Some textual restructuring can make graphical identity or layout preservation ambiguous. This is a known limitation of bidirectional projective editing.
Local service cannot be reached	Browser security restrictions can prevent access to arbitrary local services. Verify that the service is running and that its endpoint is accessible from the browser.
Remote Flexo/MMS connection fails	Verify the configured server URL, authentication, network/VPN access, and server availability. Check the Kotar service logs for additional information.
Model changes cannot be committed to Flexo	Verify that the model is valid and that the Flexo repository/service is available. Invalid intermediate model states may remain in the local/Git workspace without being promoted to Flexo.
Git operation fails	Verify repository configuration, credentials, remote URL, branch permissions, and netwofwebrk connectivity.
SPARQL query appears to be missing SysML properties	Direct SPARQL queries operate on the minified RDF representation. Some derived SysML properties are reconstructed by the SysML v2 API and are therefore not directly present in RDF.
Query does not execute as expected	Verify the query file extension: .json/.jsonc for JSON queries, .rq for SPARQL, .sql for SQL, and .kq for KerML queries.
Kotar behaves unexpectedly after an update	Reload the application. If the problem persists, close and reopen the browser tab and workspace.
Problem persists	Check the Known Issues and FAQ. If the problem is not documented, submit an issue in the Kotar support repository.