Resolved issues
The following issues have been resolved in FortiLAN Cloud version 23.1. For inquiries about a particular issue, visit the Fortinet Support website.
The following issues are resolved in FortiLAN Cloud.
|
Issue ID |
Description |
|---|---|
| 829250 | Cloning operation failed for a network if FortiPresence was enabled. |
|
867932 |
The AP portal and Switch dashboards took a long duration to load data. |
| 869019 | Sorting by the status function did not work correctly in the Network/Switches page. |
| 869615 | FortiLAN Cloud maintained SAML credentials and displayed non-SAML accounts as SAML users. |
The following issues are resolved in Wireless (FortiAP).
|
Issue ID |
Description |
|---|---|
| 870054 | The Wireless Clients Connection Trend graph displayed incorrect data. |
| 870124 | Captive Portal SSID broadcast stopped randomly. |
| 870868 | The scheduled SSID did not beacon correctly within the configured time period. |
| 871614 | The FortiAPs were assigned incorrect tags. |
| 876174 | Configuring Radio 3 in AP mode was allowed for FAP 231F Platform Profile even when the dedicated scan was disabled. |
| 878439 | Unable to delete trunk when with spaces in their names. |
The following issues are resolved in Switch (FortiSwitches).
|
Issue ID |
Description |
|---|---|
| 857343 | Sometimes, FortiSwitches remained in the Connected state and did not progress into the Online state. |
|
882087 |
FortiSwitch tag name between '<' and '>' was not displayed on the Zero Touch configurations page. |