Limitations
2 min
The following limitations have been identified. When they are resolved, they will be reported in the latest Product updates under Resolved Issues.
Upgrade and platform
- Health checks can restart Hazelcast or lem-admin repeatedly before they finish starting.
- Enrolling an SSL certificate with the webroot method in lem-cfg fails, and the change is reverted.
- Deleting images from the Docker registry does not free up storage.
- On ARM builds, the Docker network can be deleted unexpectedly.
Edge devices and activation
- Upgrading Litmus Edge from 4.0.2 to 4.0.16 through LEM can leave the device unable to boot, while LEM reports success.
- A deactivated device can fail to connect to a different LEM instance.
- Activation fails with a forbidden error when a proxy is configured on the device.
- Litmus Edge ignores a custom port in the activation URL.
- Approving an activation request can take more than two minutes.
- Gateway device metrics can be intermittently unavailable.
- You cannot stop or cancel a running task.
High availability
- The backup node does not reconnect after the HA configuration is deleted on the primary.
- The backup node’s LEM license expires after a failover.
Remote access
- Remote UI access can fail even when the status shows connected.
- Downloads through the remote tunnel can fail.
- Reloading remote connectivity in inspectable mode can fail, and the tunnel does not restart.
Templates and Git sync
- Git sync fails for devices that contain flows.
- Merging onto an encrypted template reports every secret as a conflict.
- For v1 parameterized templates, defaults are ignored and you can apply the template with all values blank.
- Template JSON shows incorrect createdAt and updatedAt values.
Digital Twins and Asset Hub
- Deploying a Digital Twin instance with parameters to Litmus Edge 4.0.0 fails with no clear error.
- When a non-admin user creates a model, the error message has no valid status code.
- The Asset Hub API returns 409 instead of 404 for an asset that was not imported.
Marketplace and applications
- Application conflict errors (409) have an empty message.
- The Delete icon is cut off on the Marketplace tabs dialog.
Alerts and logs
- The Labels filter on the Alerts page does not work.
- Forwarded logs do not include the device hostname.
Admin Console, users, and SSO
- Azure Entra ID sign-in fails for users previously registered with the same username.
- The Add button for MQTT accounts toggles between enabled and disabled.
API
- The subtask logs API fails unless both requestedPage and pageSize are sent.
- An unsupported HTTP method returns 500 instead of 405.