---
title: Limitations
slug: litmusedge/resources/limitations
description: Review the list of identified limitations that are scheduled to be resolved.
docTags:
createdAt: 2023-09-15T18:10:14.293Z
---
The following limitations have been identified. When they are resolved, they will be reported in the latest [Product Updates](docId\:RGohkxkYN_PAMu2kgYFZK) under *Resolved Issues*.
| Description |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **DeviceHub:**
* In the *Create Browse Task* dialog, the OPC UA Client Advanced driver's exclusion list checkboxes display on one line instead of in a list when browsing for tags.
* In grid view, *IP Address*, *Port*, or *Station ID* may not display in device cards. Refresh the page to show the missing values.
* DeviceHub user role permissions cannot be modified after they are saved. As a workaround, remove and recreate the role. |
| **Analytics:**
* Memory usage can remain high after you delete a TensorFlow processor.
* Litmus Edge validates models only for archive format. Litmus Edge does not verify that a model is loadable, or that the Input/Output operation names configured on the TensorFlow processor exist in the model's signatures. The processor saves without error, and any mismatch surfaces only as a load-time error when the source is enabled. As a workaround, run `saved_model_cli show --dir --all` to confirm the exact operation names before configuring the processor. Names are case sensitive and must come from the same signature.
* FileReader processor is unable to read files that are generated from Flows Manager. As a workaround, in Flows use the exec node to run `chmod` commands to update file and directory access.
* The first flow created in Flows Manager cannot be stopped or restarted in Safe Mode. |
| **Integration:**
* CSV imports incorrectly allow topic names that end with trailing dots.
* After upgrading to 4.0.16, Gen 2 connectors might start in a disabled state and require you to manually enable them.
* If the target disk for a PostgreSQL Gen 1 connector fills up, the connector may not recover on its own once space is freed. This does not affect the PostgreSQL Gen 2 connector.
* For Gen 1 connectors, corrupted buffer data after an unexpected shutdown can affect specific connectors' persistent storage. As a workaround, purge the persistent storage data.
* 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. |
| **OPC UA:**
* When two nodes in different paths share the same name or ID, deleting or renaming one can instead incorrectly apply to the other. In addition, no error message displays. |
| **System:**
* 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.
* Importing a template with multiple connectors fails when a configuration issue occurred with one component. |
| **Docker:**
* On Litmus Edge Docker containers activated against a Litmus Edge Manager site license, the Backup and Updates features may incorrectly appear as unlicensed. Node-locked licensed containers are not affected. |