Known Issues

Known Issues contain descriptions of the issues and workarounds, when available. Check this document periodically to stay informed of updates and other new information.

The following Known Issues are present in this release. Once resolved or redetermined as a non-issue, they will be moved to the following Fixed Known Issues section.

  • Static IP assignments for Wi-Fi clients may not be retained after being applied in Devices tab> Manage Devices drawer. When this occurs, the Edge continues assigning the client an IP address from the dynamic DHCP range instead of the configured static IP address.
  • When editing an Edge node location in Edge Item Overview > Location, changing the Edge will be moving setting may cause the location update to fail. As a result, the updated location is not saved when that setting is changed during the edit.

    Workaround: Update the location address or coordinates without changing the Edge will be moving setting. The location update succeeds as long as that setting is left unchanged.

  • When drilling down from the In Use Hardware by Connectivity Status chart for the In Use Cellular Edge with Network Priority bar graph to the Inventory page, the Connectivity Type filter chip may not be applied automatically. As a result, the Inventory table may display unexpected results that do not match the selected chart segment.

    Workaround: On the Inventory page, manually add the Connectivity Type = Cellular filter chip in the search bar to display the expected filtered results.

  • After a successful Replace Edge operation, Zero Touch Activation may fail on the replacement edge. When this occurs, the replacement edge is unable to complete activation successfully, including when using broadband, Cellular SIM1, or Cellular SIM2 for connectivity.
  • Bulk onboarding of large edge batches may fail in some cases. Smaller batches can complete successfully, but onboarding requests involving 50 or more edges may encounter failures during processing. Workaround: If bulk onboarding fails for a large batch, retry using smaller onboarding batches instead of submitting all edges in a single request.
  • After power recovery, the Cloud Connector cellular interface may enter an ERROR state in the ECP UI. When this occurs, configuration updates may fail to apply to the Cloud Connector.

    Workaround: Reboot the Cloud Connector. Once the cellular interface no longer shows ERROR and returns to a Connected or Disconnected state, retry the configuration update.

  • After changing the APN for a Cloud Connector, the cellular connection may not re-establish automatically. In some cases, the Cloud Connector remains disconnected until the modem connection is reset or the device is power cycled.

    Workaround: Avoid changing the APN unless necessary. If an APN change is required, power cycle the Cloud Connector after updating the APN so the cellular connection can be re-established.

  • For some applications, primarily Windows applications, the Version field in Hardware Groups may display null in the Applications tab and in the edit application dropdown when version information is unavailable. This is a display issue only; the application version should be interpreted as unavailable rather than as an actual null value.

    Workaround: If the Version field displays null, treat it as version information being unavailable. You can continue working with the application entry, but the displayed version value may not be reliable until this UI issue is resolved.

  • If a device's SIM is in the Activation Ready state, attempting to deactivate the device from the UI may fail with a generic error message. In this case, the device remains active, and the UI does not explain that the SIM must first move to a supported state before the device can be deactivated.
  • Do not manually change the APN on a Cloud Connector with cellular connectivity configured, as selecting a different APN can cause the Cloud Connector to lose cellular connectivity and become disconnected.

    In case this happens, access a Cloud Connector's local UI (once it is disconnected from the ECP Cloud service) to correct the APN / Preferred SIM configuration back to the expected/default values for the active SIM and plan.

  • In the inventory view, connectivity icons may not always match the reported connectivity state for a device. For example, a device may show a Connected state while still displaying a warning icon. This is a display synchronization issue in the UI and may cause temporary inconsistency between the status text and the icon shown.

    Workaround: If the connectivity icon and status text do not match, open the device details or overview page and use the most recent connectivity status shown there as the source of truth. Refreshing the inventory view may also help bring the icon and displayed state back into sync.

  • In Storage Management, the maximum database size may sometimes be shown as higher than the actual value. This is a display-only issue and does not affect the actual storage allocated to your database.
  • While the site is loading, especially on slow internet connections, the bottom menu may briefly show Chinese or Arabic characters in place of icons. These characters are replaced by the correct icons once the page fully renders.
  • When setting a short inactivity threshold (e.g., 1-2 minutes) for cellular devices without sensor attributes, warnings may be generated based on SIM polling data (every 15 minutes), rather than actual device inactivity. This can lead to unexpected warnings even when no sensor data is available.
  • On the dashboard, the Edge Nodes Onboarded in the Last 30 Days chart may display dates and data points from before your tenant was onboarded. No actual onboarding activity will be shown for those earlier dates, but they may appear on the chart until this issue is resolved.
  • Suspended customer tenants may not show up in the Storage Management screen.

  • The number of warnings for Edge Nodes appearing in the Issues tab may be inaccurate.

  • Some Hardware Groups' devices, applications, and configurations are not getting successfully updated on the MDM-provider side, especially when changing the hardware group name in Oracle ECP.
  • After onboarding an IoT Device with cellular connectivity, the device item overview page intermittently reflects a delay of several minutes for data, sms, and voice to be displayed.
  • Occasionally when mobile data is disabled on a cellular device, the ECP UI will reflect an incorrect connectivity state. This is MNO dependent.

  • Action drawers may not reflect the latest data available in ECP if the item overview page displays older data when opening that drawer.

    Workaround: Load the latest data using the refresh button before opening the drawer. Alternatively, after opening a drawer, if you see old data, close the drawer and refresh the item overview and reopen the drawer for further operation.

  • Across the UI and within downloaded reports, ECP uses different units when displaying the time. Downloaded reports are in UTC time and dashboard time presentations with a "Z" or "UTC" are also in UTC time. If the UI presents a time without a Z, it should be interpretted as local time.