Limitations

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 analytics wire connection types default to events for processors that support both types, when uploading a template or after an upgrade application when upgrading an app from litmus edge manager, the running container can be stopped before the new image is fully downloaded launching certain marketplace apps with named volumes creates an extra unused docker volume the container terminal returns a blank page when attempting to output raw binary data 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 results are not returned when filtering by a large number of inbound subscriptions for a connector 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 a size limit exceeded error occurs when the system generates a high volumes 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 support bundle downloads can fail with a you provided 'function text() { \[native code] }' where a stream was expected error cloud storage sync jobs to databricks volumes may incorrectly fail after only 30 seconds of network note that synchronizations are restored at the next trigger interval applying a template that includes authentication or device management proxy configuration can cause a partial restore error importing a template with multiple connectors failed when a configuration issue occurred with one component in some case, a failed to check firmware upgrade status max retry attempts exceeded error displays in litmus edge manager after upgrading a litmus edge device even though the device is upgraded successfully the system reports a success status during litmus edge manager activation, even when all individual underlying network tests have failed high availability changes in network > interfaces are not reflected on the backup node proxy urls are not preserved after a software update in system > network > proxy proxy urls configured on the primary node are not copied to the high availability backup node