Known Issues and Limitations¶
This article lists the known issues and limitations of EnOS.
Application Portal¶
| Issue Description | Workaround | Discovered On |
|---|---|---|
| The logs on assigning or removing assets do not appear in the audit log list. | None | 2023/02 |
| In an exported audit log file, the Resource Type of Export Users events is “null”. | None | 2023/02 |
Data Synchronization¶
| Issue Description | Workaround | Discovered On |
|---|---|---|
| The SFTP data source is unable to synchronize its structured data from the database to the EnOS Hive data warehouse. | Use an FTP data source to implement data synchronization. | 2023/12 |
| The FTP data source using FTPS protocol is unable to synchronize its structured data from the database to the EnOS Hive data warehouse. | Use an FTP data source to implement data synchronization. | 2023/12 |
Time Series Data Management¶
| Issue Description | Workaround | Discovered On |
|---|---|---|
| Modify TSDB storage policy storage duration: If the data size of the table corresponding to this storage bucket is large, it will take a long time to update the storage duration, and the data under this table may not be available for TSDB service during the update period. | None | 2023/02 |
Device Data Integration Service¶
| Issue Description | Workaround | Discovered On |
|---|---|---|
HTTP Client & Refresh Token node: If you select POST (also PUT and DELETE in HTTP Client node) in Request and enter Content-type in the key of Headers, the value you entered will be overwritten by the default value application/json; charset=UTF-8, which has no effect on other keys. |
Import the custom-node.zip to create a custom node to customize the value in Content-type key. |
2023/02 |
Alert Engine¶
| Issue Description | Workaround | Discovered On |
|---|---|---|
| Occasionally, alert records may be lost when a large amount of delay alerts occur continuously in a certain time period. | None | 2023/02 |
Onboarding Tool¶
| Issue Description | Workaround | Discovered On |
|---|---|---|
| Business Tag Tool: If user A failed to tag, and then user B tagged successfully. Tagged By in the Tagged Log will show user A who tagged last time instead of user B who tagged this time. This does not affect the operation and the tagged results. | None | 2023/02 |
AI Studio¶
| Issue Description | Workaround | Discovered On |
|---|---|---|
| Git is unavailable for Notebook instances using Azure storage. | Use Ceph storage instead. | 2023/02 |