Troubleshoot on CAST Imaging Documentation

Graph Fails to Load

Mon, 01 Jan 0001 00:00:00 +0000

Symptom

The canvas shows an error: “Failed to get graph data”, or the application loads but the canvas stays empty.

Likely causes

Cause	How to confirm
Neo4j out of memory	Check Neo4j logs for OutOfMemoryError or GC overhead
Neo4j page cache too small	Graph loads but is very slow; Neo4j log shows cache misses
Corrupt import	Some applications load but one specific application fails
Neo4j service stopped	CAST Imaging admin panel shows Neo4j as down

Resolution

Increase Neo4j memory

See Manage Neo4j — Optimize memory allocation.

Search Returns Stale or Missing Results

Mon, 01 Jan 0001 00:00:00 +0000

Symptom

Objects that exist in the graph do not appear in the search results.
Search results contain objects that were removed in a recent re-import.
After an upgrade, search results are incomplete.

Likely causes

Cause	How to confirm
Search index not updated after import	Compare a known object name against what appears in search
Failed ETL run	Check the import logs for errors
Index corrupted during upgrade	Problem started after an upgrade

Resolution

Rebuild the search index

See Rebuild the search index.

Source Code Viewer Shows No Content

Mon, 01 Jan 0001 00:00:00 +0000

Symptom

You right-click an object and select Show source code, but the Legend panel shows nothing, shows an error, or shows “Source code not available”.

Likely causes

Cause	How to confirm
Source code viewer not configured	Admin Center → Source Code Viewer shows no path configured
Path mapping incorrect	The path in the configuration does not match the actual file location
HTTP header restriction	Browser console shows a blocked request (CSP or X-Frame-Options error)
Source files not accessible	The server cannot reach the path where source files are stored

Resolution

Configure the source code viewer

If the viewer is not configured, set it up. See Set up the source code viewer.

Transaction or DCG Is Marked as Huge

Mon, 01 Jan 0001 00:00:00 +0000

Symptom

In the Transaction or Data Call Graph scope, an item in the list is marked with the message: “Huge Transaction, content is filtered” or similar. When you select it, no graph is displayed.

Cause

During the import process, CAST Imaging found that this transaction or data call graph contains more than 10,000 objects. The importer stopped processing it to prevent performance problems. The detail of this transaction is not available in the graph.

AI Features Are Unavailable or Return Errors

Mon, 01 Jan 0001 00:00:00 +0000

Cause	Resolution
AI features disabled for the tenant	Admin: enable AI features in the Admin Center for this tenant. See Set up AI integration.
API key not configured	Admin: add an OpenAI or Azure OpenAI API key in the Admin Center.
Role does not have access	Check the user’s role and resource permissions.

Symptom B: AI error messages

Error message	Cause	Resolution
“There is no internet connection”	The server cannot reach the AI provider	Check outbound internet access; whitelist `api.openai.com` (OpenAI) or `<app>.openai.azure.com` (Azure) on port 443
“Invalid GPT key”	The API key is wrong or has been revoked	Admin: replace the API key in the Admin Center
“GPT engine is overloaded”	The AI provider is under high load	Wait a few minutes and try again
“Source code is too large to explain”	The object has too many lines of code	Use the Explain on a portion of the source code instead
API key expired or disabled	Key was revoked by the AI provider	Admin: generate a new key and update it in the Admin Center

Next steps

Set up AI integration

Performance Is Slow

Mon, 01 Jan 0001 00:00:00 +0000

Symptom

The canvas takes a long time to display objects.
A transaction takes many minutes to load.
The browser shows a timeout or connection error.
CAST Imaging becomes slow after an application with many objects is imported.

Step 1: Check Neo4j memory

Insufficient Neo4j memory is the most common cause of slow performance.

See Manage Neo4j — Optimize memory allocation.

Step 2: Reduce the view size

Very large views (many objects and links) are slow by design. Try these options:

Login or Authentication Fails

Mon, 01 Jan 0001 00:00:00 +0000

Symptom A: User cannot log in with a local account

Cause	Resolution
Wrong password	User: use the password reset option. Admin: reset the password in the Users panel. See Manage users.
Account deactivated	Admin: reactivate the user account in the Users panel.
No role assigned	Admin: assign a role to the user. See Manage roles and permissions.

Cause	Resolution
Wrong LDAP server address or port	Check LDAP host and port in the authentication configuration. See Configure authentication.
Bind DN or password incorrect	Verify the bind DN and password. Re-encrypt the password if needed.
User not in the base DN	Confirm the user exists in the LDAP tree under the configured base DN.
Group filter excludes the user	Check the group filter in the LDAP configuration.

Symptom C: Session expires too quickly

The session timeout is configured by the administrator. Ask the admin to increase it.

Upgrade Leaves the Application in a Broken State

Mon, 01 Jan 0001 00:00:00 +0000

Symptom

After upgrading CAST Imaging:

The interface does not load (blank page or JavaScript error).
Applications do not appear in the list.
A specific feature that worked before now gives an error.

Step 1: Clear the server-side cache

A stale cache is the most common cause of post-upgrade problems.

[TODO: Steps to clear the server-side cache — file location or command]

Step 2: Verify the Neo4j schema

After a major upgrade, the Neo4j schema may need to be updated.

Troubleshoot on CAST Imaging Documentation

Graph Fails to Load

Symptom

Likely causes

Resolution

Increase Neo4j memory

Search Returns Stale or Missing Results

Symptom

Likely causes

Resolution

Rebuild the search index

Source Code Viewer Shows No Content

Symptom

Likely causes

Resolution

Configure the source code viewer

Transaction or DCG Is Marked as Huge

Symptom

Cause

AI Features Are Unavailable or Return Errors

Symptom A: “Explain with AI” does not appear in the context menu

Symptom B: AI error messages

Next steps

Performance Is Slow

Symptom

Step 1: Check Neo4j memory

Step 2: Reduce the view size

Login or Authentication Fails

Symptom A: User cannot log in with a local account

Symptom B: LDAP login fails

Symptom C: Session expires too quickly

Upgrade Leaves the Application in a Broken State

Symptom

Step 1: Clear the server-side cache

Step 2: Verify the Neo4j schema