My ElastiCube build failed. It was querying a SQL Server database at the time. I looked on that database after the failure: the build still had a query open. Is that normal? Does Sisense attempt to cancel queries as part of a build failure?
Hello,
Sisense does try to cancel queries when a build fails, but it’s not perfect. If the build ends normally or is stopped manually, most queries are cleaned up. The tricky part is if the ElastiCube build service crashes or is killed unexpectedly - in that case, some queries might keep running on the SQL Server (or other DB), which is what you’re seeing.
This is actually expected behavior and not a bug. To minimize the impact, some users use short query timeouts on the database side or split large builds into smaller/incremental chunks. That way, any orphaned queries run shorter and are easier to manage.
Sisense handles cleanup when it can, but fully automatic query cancellation isn’t guaranteed if the process dies unexpectedly.
