Resolving "Connection is Missing" during ElastiCube builds in multi-tenant environments [Linux]
Introduction
In multi-tenant Sisense, a Data Designer may hit intermittent 3404 "Connection is Missing" build errors that reference the wrong tenant's connection, while an admin builds successfully. This guide explains why connection scoping causes it and how to fix it.
Step-by-Step Guide
Why this happens
In multi-tenant Sisense, connections are isolated per tenant and per owner. The 3404 "Connection is Missing" error at build time means the build service cannot resolve the connection OID within the scope of the user running the build. When a Data Designer does not own or cannot see the connection the cube references, resolution falls back and intermittently binds to the wrong tenant's connection - which is why the reported missing connection changes between build attempts with no changes to the cube. An admin succeeds because admin visibility spans all connections.
Step 1 - Share the connection with the Data Designer
As an admin, go to Admin → Data → Connections. Open the connection the cube uses and share it with the Data Designer user. Grant access with edit rights so builds can resolve it. Repeat this for every connection the cube references.
Step 2 - Verify tenant scoping while sharing
Confirm the Data Designer is operating in the same tenant the connections belong to. Also confirm that no same-named connection exists in another tenant, since duplicate names across tenants can cause the build service to bind to the wrong one.
Step 3 - Refresh the connection binding (if sharing does not clear it)
If the error persists after sharing, re-bind the connection at the table level. For each affected table: Change Table → re-parse the SQL expression → Done. This forces Sisense to re-resolve the connection binding for that table.
Conclusion
Cross-tenant 3404 “Connection is Missing” during builds are almost always a connection-scoping and permissions issue rather than a broken cube. Sharing every referenced connection with the building user, verifying correct tenant scope, and re-binding table connections resolves the error. The key takeaway: a non-admin build user must have visibility of every connection the cube depends on.
References/Related Content
