Troubleshooting
|
This is the public preview documentation of Neo4j Virtual Graph. To provide feedback, please use the feedback form you were granted access to. During the public preview, we advise you not to use sensitive or production data with Virtual Graph. |
This page contains common troubleshooting guidance for Virtual Graph setup and import.
Common issues and checks
Data source and authentication
Verify that the data source is supported and that the connection details are correct.
Check whether the following are true:
-
The data source type is correct
-
The correct authentication method is configured
-
The data source account has the required permissions
-
The target environment can reach the data source
If authentication is ambiguous or multiple methods are available, document which option was selected and what credentials were used.
Model and importer configuration
The graph model and importer settings must be consistent with the source data.
Check the following:
-
You have mapped the data source tables which you want to virtualize to suitable labels and relationship types
-
The selected import configuration matches the data source schema
If the model cannot be inspected directly, capture the importer UI state and the relevant screenshot.
Data quality requirements
Virtual Graph imports can fail when the input data does not match the expected graph model.
Make sure that:
-
Labels use unique keys where required
-
Relationship types use unique keys where required
-
Relationship and node labels are used consistently
-
There are no duplicate or conflicting identifiers
For example, if a label is expected to be unique by key, confirm that the imported records do not produce duplicate keys for that label.
Support Requests
When a Virtual Graph setup or import fails, it can accelerate your support case if you collect the following information:
-
Your type of data source
-
Your authentication method, including multi-factor or service account details
-
Your model and/or graph structure
-
Whether you created your model in the importer UI or via an existing model
-
Screenshot of the importer or model configuration, if available
-
Labels and relationship types used in the import
-
Whether key fields are unique on labels or relationship types