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.

Issues apply to all personas unless otherwise specified.
  • Occasionally, provisioning a new ECP environment may stall and take up to 4 days to complete. If this occurs, periodically check the My Applications page in OCI to confirm when the environment status indicates it is ready for your initial log in.
  • When generating Cloud Connector platform logs, if you select a start time that predates the Cloud Connector’s activation/onboarding, no logs are produced and you may see a “no files found for the specified time range” error.

    Workaround: Ensure the Cloud Connector is powered on and choose a start time after activation/onboarding (within the next 1–24 hours).

  • Do not deactivate a Starlink terminal in ECP and then attempt to Activate it again during the prorated (partial) billing month (for example, the month in which the terminal was initially activated mid-cycle), because re-activation may fail due to Starlink plan proration behavior. This limitation does not affect initial Starlink onboarding/activation or changing the service plan.
  • 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.

  • On the Applications Tab of the Device details page, you may see an older version of the application listed instead of the latest version.
  • The Update in Progress banner may display incorrectly on the Cloud Connector Item Overview. This is a display-only issue; the banner can be ignored if you are not actively performing an update.
  • A device using the Cloud Connector for connectivity may show Connected in the Cloud Connector's Devices tab, but when you open that same device's Overview page, the connectivity status may display as Disconnected. This is a UI/status synchronization issue; refresh the pages and use the most recent device check-in/connectivity indicators to confirm the current state.
  • When adding applications and configurations to a Criteria-Based Group with no criteria defined, the added items are initially visible but are automatically removed from the Group after approximately 2-5 minutes without user intervention. This results in the unexpected loss of group app and configuration assignments, and persists unless explicit group criteria are set.
  • Groups you create on the Hardware Groups tab are limited to 30 characters in length.
  • 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.
  • When performing the "Wipe and Deactivate" action on a Windows device, the device lifecycle state does not transition to Inactive as expected; additionally, after re-enrolling the device, its lifecycle state incorrectly remains Inactive instead of moving to Active. This results in inaccurate lifecycle status following wipe and re-enrollment actions.
  • 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.
  • On the dashboard, the Devices 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.
  • 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.
  • The Usage Per MNO Account (Last 30 days) table on the Dashboard screen may reflect more than 30 days of data.
  • 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.