Resolved Issues
The following important issues have been fixed in FortiSOAR release 7.6.4. This release also includes important security fixes. To inquire about a particular bug, please contact Customer Service & Support.
Graphical User Interface
| Bug ID | Description |
|---|---|
| 0947048 | Fixed an issue where the Select a Field drop-down list did not display a scroll bar when using Create Advanced Grid Filter in module grids (e.g., Alerts). |
|
1150477 |
Fixed an issue where record sorting was displayed incorrectly in module grids (e.g., Incidents) after applying filters and then removing them from the GUI using "Clear All" or "Clear Filter Criteria". |
|
1157483 |
Fixed an issue where the data table was not reset (i.e., not hidden) when switching from a chart that supports data tables (e.g., Bar or Pie chart) to one that does not support them (e.g., Donut chart). |
|
1173226 |
Fixed an issue that prevented adding visibility conditions to picklists in custom modules. |
|
1175148 |
Fixed an issue where using the "Clear All" button to remove default filters broke the default sorting on the grid. |
|
1177294 |
Fixed an issue where users were unexpectedly logged out of active sessions in FortiSOAR after upgrading to release 7.6.2. |
|
1182042 |
Fixed the issue with the Timeseries widget not displaying months or fields with no data, instead of showing a value of 0. Now, the Line and TimeSeries charts support rendering as a continuous monthly series—even when some months have no data. |
|
1190127 |
Fixed an issue where the 'View Password' (eye) icon on the FortiSOAR login page did not toggle the password visibility when a browser-based password manager extension (e.g., LastPass or NordPass) was enabled. |
Playbooks & Connectors
| Bug ID | Description |
|---|---|
| 0970165 | Fixed an issue where the vertical scrollbar in the Playbook Designer did not respond to mouse input and only worked with the keyboard. |
|
0986751 |
Fixed an issue where playbooks configured as 'Private' did not retain their privacy setting or the |
|
0990406 |
Fixed an issue where multiple versions of the same connector (e.g., 4.2.0 and 4.2.3 of the Exchange connector) were occasionally displayed in the FortiSOAR UI after an upgrade. |
|
1059984 |
Fixed an issue where playbook imports failed with the error message "Some of the Playbooks already exist." even when the playbook was not present. This issue occurred when a playbook step, part of a playbook group, was exported and imported into another system, but the playbook containing the group did not exist. Now, during import, if a playbook step contains a group IRI that does not exist in the current playbook, the IRI is set to null, and the import proceeds successfully. |
| 1078777 | Fixed an issue where errors were shown instead of the connection status when using the 'Test Configuration' button with invalid configurations while creating or editing a custom connector. |
|
1142314 |
Fixed the health check failure on the Master node for connectors configured on Agent or Tenant. This issue occurred when traffic was initiated from the Master node, and both the Master and Tenant nodes used proxies. |
|
1155786 |
Fixed an issue where the Manual Input form became unresponsive — text could not be selected, no cursor appeared, scrolling was disabled, and text was hidden. The form would only become responsive again after toggling to full screen and back. The issue was caused by the Markdown editor and has now been resolved. |
|
1191496 |
Fixed an issue where opening the 'Executed Playbook Log' from a record detail page or the Playbook Designer page incorrectly applied a filter to the 'Historical Playbook Logs'. Now, when accessed from these pages, no filters are applied to either 'Historical Playbook Logs' or 'Recent Playbook Logs'. However, the global 'Executed Playbook Log' applies filters to both log types to display logs beginning 24 hours prior to the current time. |
|
1129173 |
Fixed an issue where playbooks remained indefinitely in the "awaiting" state when the FSR Agent failed to respond. A scheduled task has been added to the |
|
1191119 |
Fixed an issue where the Field Mapping screen became unresponsive when updating a module (e.g., Alert > Incident) in the Data Ingestion Wizard. The fix adds lazy loading for fields and initially displays rich text fields as text inputs, which users can toggle to rich text view. |
System & Security
| Bug ID | Description |
|---|---|
|
1068738 |
Fixed an issue where users were incorrectly redirected to the FortiSOAR login screen when SSO was initiated from the Service Provider (e.g., Okta). This occurred when users did not log out properly—such as closing the browser directly—leaving an expired token in the browser. On the next login attempt, FortiSOAR used the expired token instead of the new one, causing the login screen to appear. FortiSOAR now correctly uses the new token, enabling seamless login without displaying the login screen. |
|
1127495 |
Fixed an issue where users were unable to log into the FortiSOAR UI after the administration disabled 2FA configuration or the 2FA mandate at the global level. Users used to encounter the error: |
|
1183076 |
Fixed an issue where, when updating a field using Advanced Edit (Jinja2) with the Append option selected as the update method, the field was incorrectly overwritten instead of appended. |
|
1185741 |
Fixed an issue where assigning a custom role to an existing user incorrectly overrode the user’s existing roles and permissions for certain modules. |
CLI & API
| Bug ID | Description |
|---|---|
| 1200233 | Fixed an issue where the csadm ha show-health --all-nodes command and /api/auth/cluster/health/ API returned a "TypeError: 'builtin_function_or_method' object is not subscriptable error" The command and API now correctly return the expected health details. |
|
1141317 |
Fixed an issue where authentication with the HMAC token failed due to an unnecessary port number being appended when copying the API route in the Custom API Endpoint playbook trigger. |