Fixed Known Issues

This section lists previously-open known issues that are now fixed. Issues closed prior to the previous major release will gradually age out and be removed from this list.

Fixed in this release:

  • 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.
  • 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.
  • Groups you create on the Hardware Groups tab are limited to 30 characters in length.
  • 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.
  • 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.
  • 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.
  • The Usage Per MNO Account (Last 30 days) table on the Dashboard screen may reflect more than 30 days of data.

Fixed in the previous release:

  • When the telemetry data for Edge or Edge services is requested, there will be a lag of approximately 4 minutes in the data being displayed.
  • UI will reflect an delayed update of the Latest Data Session Start and Latest Data Session End fields in the More Information drawer's cellular tab due to the MNO for Vodafone SIMs.
  • When onboarding cellular devices, if multiple APNs are configured for a CSP, internet and messaging services may stop working.

    Workaround: restrict cellular devices to a single APN per CSP.

  • For cellular devices and Cloud Connectors using AT&T service, the ECP UI does not validate between the Network Priority checkbox and compatible APNs. If there is a mismatch, the user could be charged at a higher rate while receiving standard data prioritization. Only the following APNs listed in the UI support Network Priority.
    • ecp.oracle.com (QoS)
    • ecp.t.oracle.com (QoS)
    • nxtgenphone (QoS)

    Workaround: Ensure that the above APNs are not associated with devices where Network Priority is not expected.

  • The Customer filter chip must not be removed from the Cloud Connector or Device Inventory page's Search box.
  • The top 5 applications shown on the Application memory usage graph shown in a Cloud Connector's Overview Tab, are not necessarily the top 5 running on the Cloud Connector itself.
  • On a Device's Application tab, after clicking Sort Ascending or Sort Descending, the application list displays 'There are no applications associated with this device.'
  • Not all Applications added in Hardware Group are reflected in applications tab of associated device.
  • For non-MDM cellular devices with single SIMs, after deactivation, the SIM state according to the MNO is not updated on the UI.
  • Cloud Connectors and Devices assigned to customer tenants may appear in the inventory, even after the tenant is suspended.
  • Monthly and daily warnings for data and SMS usage appear identically on the UI.
  • When using the Add Hardware guided flow, when choosing a target customer to onboard the hardware, the first click is not accepted. Workaround - click the customer name a second time on the drop down value.
  • When navigating to a Cloud Connector's details page from a Satellite Terminal row's Edge Node column on the Satellite Terminals Inventory page, that Cloud Connector's actions are immediately visible on a single line rather than only being accessed by clicking the Actions menu.
  • When MNOs return multiple bearers, the cellular connection is not set up properly.
  • When the browser is set to a relatively small width and the bottom-most bar responsively changes to move all tabs that don't fit under a "..." option, when clicking the hidden tabs from under the "..." option, the redirections to the appropriate pages are incorrect
  • Device details downloads may not include the most recent fields and structure.
  • The top-application-usage API reports a 500 error code on a Resource Type error instead of reporting a 404 error.