Known Issues and Workarounds

• 1132542: After upgrading a FortiSOAR deployment configured with Multi-Tenancy (MSSP) and High Availability (HA) in an Active-Active cluster, the WebSocket connection on the secondary node remains disconnected.
  Workaround:
  Restart the cyops-tomcat service on the secondary node:
  #systemctl restart cyops-tomcat
  This restores the WebSocket connection on the secondary node and ensures that all nodes are properly connected.
• 1175148: After clearing the default filters, the default sorting functionality for the Grid widget is broken in FortiSOAR 7.6.2.
  This issue will be resolved in the next FortiSOAR release.
• 1177294: After upgrading to FortiSOAR 7.6.2, users occasionally get logged out of active sessions.
  This issue will be addressed in the next FortiSOAR release.
• 1182042: The Timeseries widget does not display months or fields with no data, instead of showing a value of 0. For example, if a month has no records, it is omitted from the timeseries chart. Similarly, if there are no records for a specific field (e.g., no records with 'Critical' severity), the corresponding column is not displayed in the table.
  This issue will be addressed in the next FortiSOAR release.
• 1183076:When updating a field using Advanced Edit (Jinja2) with the 'Append' option as the update method, the field is overwritten instead of being appended. The 'Append' option does not take effect, and the 'Overwrite' method is applied instead.
  This issue will be addressed in the next FortiSOAR release.
• 1185741: When custom roles are created and assigned to an existing user, they may override that user’s existing roles and permissions for certain modules.
  This issue will be addressed in the next FortiSOAR release.