Resolved Issues
The following important issues have been fixed in FortiSOAR release 7.6.5. This release also includes important security fixes. To inquire about a particular bug, please contact Customer Service & Support.
Graphical User Interface
| Bug ID | Description |
|---|---|
|
1095054 |
Fixed an issue where applying advanced filters caused earlier column-level filters to be retained on grids. When an advanced filter was combined with column-level filters (for example, status = open), results displayed correctly, but after selecting Clear All, refreshing the grid, and reapplying advanced filters, the previous column-level filters persisted. |
| 1212939 | Fixed an issue where mouse scrolling did not work correctly when users scrolled to the extreme left or right of a grid. FortiSOAR would navigate to the previously visited pages (back or forward) instead of remaining on the current page, which prevented proper scrolling. |
|
1222226 |
Fixed an issue where tags added to comments in the Collaboration Panel were not visible after reopening the record. |
|
1231024 |
Fixed an issue where dashboards using the Summary widget displayed zero records when upgrading from versions earlier than 7.6.4 (e.g., 7.6.1) to release 7.6.4. |
Playbooks & Connectors
| Bug ID | Description |
|---|---|
|
1054897 |
Fixed an issue where playbooks would enter the "Incipient" state when there were a large number of playbooks and historical logs. |
| 1199787 | Fixed an issue with reference playbooks containing a 'Manual Input' step. Previously, if the reference playbook failed at any step, the parent playbook was marked as failed, even if the "Ignore Error" option was enabled for the referenced step in the parent playbook. Now, if the reference playbook fails, the parent playbook will continue and be marked as 'Finished with Error.' |
|
1148809 |
Fixed an issue where playbooks could remain in the Awaiting state when a Wait step was configured for less than 60 seconds. The task now stays with the current worker instead of being re-queued, preventing playbooks from getting stuck in the Awaiting state. |
|
1203480 |
Fixed an issue with hierarchical picklists in playbooks (defined using JSON). Previously, when a parent category was selected and a child option was chosen, changing the parent category did not refresh the child picklist. As a result, the previously selected child options remained visible instead of updating to reflect the new parent category selection. |
|
1206575 |
Fixed an issue where a scheduled playbook for storage space reclamation failed if the activity was already in progress when the playbook was triggered again. Now, in this scenario, the playbook correctly returns an “In Progress” status instead of failing. |
System & Security
| Bug ID | Description |
|---|---|
|
1220039 |
During a rolling upgrade, the takeover operation failed when a node attempted to rejoin the cluster because one or more files under /var/lib/pgsql/16/data/ were not owned by postgres:postgres. Since the PostgreSQL data directory did not meet the required ownership constraints, the cluster join process was aborted.
This issue is resolved by adding an ownership-validation check that ensures all files in the directory have the correct ownership before the node attempts to rejoin the cluster. |