Why this happens
A data plane is the infrastructure where your data physically resides and where queries execute. Narrative’s architecture separates data planes to enable:- Data residency compliance — Keep data in specific geographic or organizational boundaries
- Security isolation — Maintain separate security perimeters for different data sources
- Infrastructure flexibility — Run data planes on different platforms (Narrative-hosted, Snowflake, Spark)
Troubleshooting steps
1. Identify which datasets are in different data planes
Review your query and identify all datasets referenced. In the Narrative platform:- Navigate to the dataset catalog
- Check the data plane assignment for each dataset in your query
- Note which datasets belong to different data planes
2. Modify your query
Once you’ve identified the issue, you have two options: Option A: Query datasets separately Run separate queries against each data plane and combine results outside of NQL:- Creating a materialized view that copies the necessary data to a single data plane
- Working with your Narrative representative to consolidate datasets
Data movement between data planes may have compliance implications. Consult your data governance team before moving data.
Related content
Data Planes
Understand where your data lives and is processed
Query Processing
How queries flow from submission through execution
Control Plane
How Narrative orchestrates across data planes
NQL Troubleshooting
Overview of common NQL errors

