Automation stitch does not work when logdevice type is FortiMail.

"Ioc_Rescan" tag does not show up for the rescanned Compromised Host under the FortiSoC.

Incidents cannot be modified.

Running AV scan playbook takes long time to load for all the endpoints and users cannot see any progress bar.

Error Message "403 Client Error" is seen when configuring FML connector under the Connectors.

The "User Data Flow" does not display the device name under the Traffic.

The gateways for clients are not plotted properly in Monitors under the "Top Dialup VPN".

"Domain" and "Category" tabs are empty for "Top Sources" and "Top Sources Addresses".

SD-WAN widgets does not display data properly.

FortiAnalyzer fails to complete FortiGate log query when filter is set using dropdown menu with value entered manually.

The log browse device list does not display all the devices.

"dstowner" field is not allowed for filter in traffic Logs.

Policy Analyzer application exists on the MEA of FortiAnalyzer.

FortiAnalyzer should try to connect to FortiClient or forticlient-emsproxy.forticloud.com when enabling EMS cloud.

Not able to get device connection stats using SNMP get.

IOC module uses too much memory.

SIEM daemons are still running even if SIEM module is disabled.

FortiAnalyzer in the collector mode did not forward syslog to the Splunk server.

Logs related to the removed devices are archived and took disk space.

"svc dvmdb reader" uses high CPU percentage.

"Device ID (devid)" does not work properly for default reports.

"Selected data binding is invalid" is shown for "Data Binding" in the chart details for "Traffic statistic".

Report's header may not be repositioned.

FortiAnalyzer displays the error message "At least one column is required." when creating a join statement from temporary tables and mapping it to a chart.

The SD-WAN Internal and External throughput values are displayed wrongly.

Date format is not applied to report cover page dates.

Scheduled per-device report cannot be completed and blocked other reports.

Unable delete an incident if the attached report was deleted from Shell.

In the local event logs, Device Name doesn't match the FortiAnalyzer's Hostname.

SSO users cannot connect to the map server.

Not able to change RAID level from GUI for FAZ300F/3000.

FortiAnalyzer can restrict ADOM access for super users.

After applying the "All Devices" filter under the log forwarding "All FortiGate" option will be showed up.

Primary FortiAnalyzer shows the secondary FortiAnalyzer hostname wrongly.

FortiAnalyzer connects to map server and GeoIP server directly even when the web-proxy is enabled.

When Forward server is disabled, user has no visibility on the log forwarding servers setting.