When FortiManager sends syslogs to FortiAnalyzer, the FortiManager device may appear twice as unauthenticated devices.

FortiAnalyzer ha-member-auto-grouping may not work FortiGate HA devices.

Device Manager may not show FortiGate Fabric members under the root Fabric tree.

SD-WAN Monitor may show incorrect bandwidth.

Top Cloud Applications may show 0 KB utilization under the Bandwidth column.

FortiView widgets may take a very long time to load.

FortiView's Secure SD-WAN and Secure SD WAN report should display correct information for Health Checker's packet loss.

Monitor should be able to show values with faster response time.

Exporting to Report Chart may fail for "Top Apps by Installs fails".

Some log files under Log Browse may contain a mix of event and traffic messages.

FortiAnalyzer should roll active logs on a weekly basis by default.

FortiAnalyzer may be missing a double quote in direction log field.

oftpd may not work properly if many log requests are received at the same time.

FortiAnalyzer may not handle many re-connection requests causing FortiGate devices log system event on disconnecting or connecting.

ADOM archive should not be higher than the configured value.

FortiAnalyzer may be showing two VDOMs, root and default, in Log Browse for FortiClient devices.

FortiAnalyzer may stop receiving logs every day until it has been rebooted.

ForiGate may show, "Failed to get FAZ's status. Authentication Failed. (-19)", when the device has been authorized and sending logs to FortiAnalyzer.

FortiAnalyzer may gradually stop to receiving logs due to leaks in receiving buffers.

FortiAnalyzer may gradually stop to receiving logs due to leaks in receiving buffers.

Drilldown compromised host from FortiGate may not work.

FortiAnalyzer should change login-max and docker-user-login-max range from 1-32 to 1-256.

SNMPv3 engineBoots may not properly be initialized.

SIEM database should be trimmed at the same time when quota enforcement occurs.

When FortiAnalyzer is changed to Collector mode, siemdb should automatically stop working.

The login interface may crash if user inputs pre-login banner text in encoding other than UTF-8.

Setting of "FortiCloud Single Sign-On" is always displayed on login.

Log disk usage may frequently reach 99% due to calculation on the siemdb size.

There may no a lot of errors showing "could not read block 0 in file" in pgsvr.log.

When rebuilding database on the FortiAnalyzer HA's secondary unit, it may stuck at 1%.

Under Microsoft Azure, FortiAnalyzer HA's secondary IP does not move to new primary after HA failover.

FortiAnalyzer may frequently send 'csf-check' requests causing miglogd consuming 99% of the CPU resources.

The sqllogd may take a long time to startup.

Disk I/O is at 100% with no log insertion due to a device is wrongly recognized as a cell phone with multiple IP addresses.

FortiAnalzyer may have incorrect dataset queries without considering the 'direction' field.

After exported report template from FortiAnalyzer 6.2 and imported the template to a later version, FortiAnalyzer may show an error, "Invalid Device or Vdom".

Customized cover page may not be consistent with the configuration preview with editor.

Scheduled report created from JSON API may not be visible on GUI.

Report may show no active users when there are logs for active users.

Restoring reports for a thousand of ADOMs may take many hours with high memory usage.

Log field list for filter may be empty with FortiClient ADOM.

FortiAnalyzer may not be able to clone SD-WAN Device-Interface Inbandwidth Line chart.

Report filtering may not work when five hundreds plus FortiGate devices are selected.

"Template Secure SD-WAN Report" may not show a graphic that includes both the "SLA Name object" and "WAN interface" fields.

"360-Degree Security Review" Report has typo in chart header, "Spayware".

When creating a log forwarding entry, user should be able to select a FortiADC device from GUI.

After upgraded FortiAnalyzer, FortiGate HA devices may get removed from the list of devices defined within the log forwarding configurations.

Changing Timezone on FortiAnalyzer does not take effect on FortiSOC.

When Device Manager's permission is set at Read-Write and System Settings' permission is set at Read-Only, SAML login user cannot create new or edit ADOM.

When FortiAnalyzer receives logs after there is an offline event, FortiAnalayzer should show status changes with event messages.

TACACS user is not able to browse Log View.

FortiAnalyzer may show ADOM that stores logs that exceeds FortiAnalyzer log storage criteria.

The forwarded CEF start time is different than the original timestamp of the log.