Failed to export dependency: datacontext/listDataContextOfDataModel - timeout of 10000ms exceeded [Linux]
Summary: Anton Diachenko discusses an error encountered when trying to export or duplicate data models in environments with numerous data security rules, where an error message stating "Failed to export dependency: datacontext/listDataContextOfDataModel - timeout of 10000ms exceeded" may appear. This issue arises because the default timeout for the dependencyExportQueueTimeoutInMs operation is set too low at 10 seconds for complex models. The author provides a solution by advising users to increase this timeout setting to 60 seconds using the Sisense Configuration Manager or via a command line adjustment. While this workaround is effective for this specific scenario, the author advises that it should be tested in the particular environment before being fully implemented to ensure compatibility, as results may vary across different Sisense versions.
Introduction:
When attempting to export or duplicate a data model, users may encounter the following error message:
"Failed to export dependency: datacontext/listDataContextOfDataModel - timeout of 10000ms exceeded"
This issue typically occurs in environments where the data model contains a large number of configured data security rules. As the volume of these rules increase, the system requires additional time to process the associated data context during export or duplication operations.
L2025.1 + Cloud/On-Prem
Step-by-Step Guide: The error is caused by the default timeout limitation configured for the dependencyExportQueueTimeoutInMs operation. By default, this timeout is set to 10,000 milliseconds (10 seconds), which may not be sufficient for models with extensive security rule configurations.
Resolution:
UI: Access the Sisense Configuration Manager from the Admin tab -> System & Hardware
Click 5 times on the Sisense logo to access the hidden configuration
Go to ECM configuration, increase the ‘dependencyExportQueueTimeoutInMs’ timeout to 60000 and save the changes.
Command line:
Access the server through the SSH and perform the following command:
sudo kubectl -n sisense exec -t "$(sudo kubectl -n sisense get po -l app=configuration -o jsonpath='{.items[0].metadata.name}')" -c configuration -- curl --request POST -H "Content-Type: application/json" http://127.0.0.1:3030/configurations/service/ecm --data '{"dependencyExportQueueTimeoutInMs": "60000"}'
Conclusion:
The timeout of 10000ms exceeded error during data model export or duplication is primarily related to processing delays caused by extensive data security configurations. Increasing the dependencyExportQueueTimeoutInMs timeout value in the ECM configuration provides an effective solution and ensures smoother handling of complex data models..
Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this, please let us know.
