| MS-24544 |
Blocker |
A brief Meraki connectivity interruption should not wrongly stop an organization's data collection, with no automatic recovery (4.3 fix) |
Previously, a brief interruption while contacting the Meraki dashboard could cause DataMagic to incorrectly treat an organization as removed and stop collecting its data. DataMagic now confirms an organization has genuinely been removed (over a sustained period, ignoring transient errors) before acting, and automatically restores any organization that was affected. A short Meraki connectivity blip no longer interrupts an organization's data collection. |
| MS-19851 |
Blocker |
Change History timeline should show new items like the table does |
Change History timeline shows changes |
| MS-23840 |
Critical |
DataMagic/Ports: Ordering by "Tx pkts/s" or "Rx pkts/s" should not show null values at seemingly random places within that order |
When sorting the Ports page by traffic columns such as Tx pkts/s or Rx pkts/s, disconnected and inactive ports will now consistently appear at the bottom of the list. Previously, these ports could show up at seemingly random positions within the sorted results due to stale traffic data being retained after a port disconnected. |
| MS-24516 |
Critical |
Subscriptions estate table should not be empty if there are subscriptions (4.3 fix) |
The Subscriptions page on DataMagic now no longer appear empty even when a tenant had subscriptions. Subscriptions and their entitlement details now load correctly. |
| MS-24509 |
Critical |
A missing MAC address on one client should not stop client data collection for the whole network (4.3 fix) |
Improved the reliability of network client data collection. In rare cases, a client reported without a hardware (MAC) address could interrupt client data collection for the rest of that network during an update. Such clients are now handled gracefully, so network client information continues to be collected consistently. |
| MS-24532 |
Critical |
DataMagic: Add composite index on OrganizationStats(OrganizationId, Created) to fix 23-second cleanup DELETE scans (4.3 fix) |
Optimised the database index used by DataMagic's automated data-retention cleanup process. This significantly speeds up routine housekeeping of historical statistics data and improves overall platform stability and reliability. |
| MS-18394 |
Critical |
Network Events Table should fill the table with expected results when lots of data is selected |
Fixed an issue where the Network Events table could appear empty when a very large data set was selected. Large result sets now render correctly, and a clear message is shown if a selection is too large to display. |
| MS-17966 |
Critical |
DataMagic: Upon Loading of Wireless Failures page a set selection should be selected when timeline is empty |
Fixed an issue where the Wireless Failures timeline could default to showing very old data (e.g. from 2023) for tenants with no current wireless failures. The timeline now defaults to a sensible, current selection; older data can still be selected manually. |
| MS-21939 |
Critical |
DataMagic: any pages which take a while to load should have a cancel button to stop processing |
Improved page-load performance across DataMagic, so previously slow-loading pages (e.g. timeline views) now load in a few seconds or less, removing the need to wait through or cancel a long-running load. |
| MS-24066 |
Major |
Column Selectors on tables with lots of columns should be fully accessible |
The column selector on tables with many columns can now be scrolled - all columns are reachable without needing to zoom out. |
| MS-22132 |
Major |
DataMagic/MacVendors: the draggable items in the column selector should be wider to fill the space in the dropdown |
The column selector dropdown in DataMagic now correctly fills the available width, making columns easier to read and select. |
| MS-24577 |
Major |
DataMagic WAN uplink quality alerts should not be be silently skipped for networks whose monitoring data arrived later than others, and a false 'back to normal' could be sent when a circuit failed completely |
WAN uplink quality alerts (packet loss, latency and jitter) are now raised reliably for every network. Previously, alerts could be silently skipped for networks whose monitoring data arrived slightly later than other networks in the same organization, and a false 'back to normal' notification could be sent when a circuit failed completely rather than degrading. Recovery notifications are now only sent when measurements genuinely return to normal. |
| MS-24649 |
Major |
DataMagic: CotermLicenseEngine oversized license JSON - increase field size |
Fixed an issue where Meraki co-term licence information could stop updating for an organisation if one licence had an unusually large number of editions or device counts. |
| MS-24632 |
Major |
DataMagic: Devices table Network column should not show "--" instead of the network name (4.3) |
On the Devices page, the Network column now shows the network name when you view devices by organization or group, with a link to the network in the Meraki dashboard. Previously the column could show a dash instead of the name. |
| MS-23877 |
Minor |
DataMagic landing page uses singular verb in "SQL powered charts enables" copy |
Corrected typo on DataMagic home page. |
