Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Known Issues

date_range 07-Mar-25

This section lists the known issues in Juniper Apstra Cloud Services.

  • When the same type of alert is generated multiple times, the alert count displayed in the Recurrence column on the Alerts page takes a few minutes to get updated. However, the alerts are displayed immediately on the Alerts page with the recurrence count as 1.

    Workaround: None.

  • In the alerts generated before onboarding Apstra Cloud Services Edge, the device name is displayed as unknown. However, alerts generated after onboarding the edge are displayed along with the corresponding device name.

    Workaround: None.

  • When the "Link Status Mismatch" anomaly occurs, the total count of services that were impacted when the link went down is displayed in the Anomalies tab. The count of impacted services in the Anomalies tab might not match the number of services displayed in the topology until the link is up again.

    Workaround: None.

footer-navigation