Limitations
1 min
the following limitations have been identified when they are resolved, they will be reported in the latest docid\ rgohkxkyn pamu2kgyfzk under resolved issues description devicehub drivers with statusregister defined by default return empty registers when devices are imported using a template analytics the first flow created in flows manager cannot be stopped or restarted in safe mode applications when a non privileged user attempts to launch a privileged application, a failed to create an application,undefined error message incorrectly displays instead of failed to create an application rejected by administrative policy privileged and some directories require additional permission integration updating the bulk insert count from 0 to any other value causes connectors to enter a failed state a bulk operation limit of 1000 exceeded error message displays when performing a bulk edit on less than 100 subscriptions system templates created in litmus edge (le) (in system > device management > templates ) that are imported into litmus edge manager (lem) cannot be applied to le instances from lem as a workaround, pull the template directly from lem and then apply it to the le instances after a system reset of an iso deployment, certain services (such as devicehub api, analytics api, and message broker) fail to initialize and remain in a failed state regardless of subsequent reboots ldap searches can return an excessive number of records resulting in an size limit exceeded error when the system generates a high volume of events from a single database file, the ui may become unresponsive in system > events additionally, csv files may not generate and download as a workaround, use apis to query events cloud storage sync jobs to databricks volumes may incorrectly fail after only 30 seconds of network inactivity note that synchronizations are restored at the next trigger interval importing a template with multiple connectors fails when a configuration issue occurred with one component high availability changes in network > interfaces are not reflected on the backup node proxy urls configured on the primary node are not copied to the high availability backup node