Without state management, scheduled playbooks may reprocess the same data.
Best practice:
Track processed items (e.g., using flags, timestamps, or IDs)
Filter only new alerts

The cleandb command with the --keep 1000 parameter removes older workflow run history entries while retaining the most recent 1000 records.

Upgrading a FortiSOAR HA cluster follows the same procedure regardless of whether it is configured in an active-active or active-passive setup. The process generally involves upgrading one node at a time to minimize service disruption. Best practices recommend upgrading the passive secondary node first before moving to the active primary node. This sequence helps maintain cluster stability and ensures that at least one node remains operational during the upgrade.

In FortiSOAR, when a user is configured with "Concurrent" access type, their ability to log in depends on the availability of concurrent user seats. This means the user can only log in if there are available seats in the concurrent pool. If all seats are occupied, the user must wait until a seat becomes free. This configuration allows multiple users to share a pool of licenses, making it suitable for environments where not all users need constant access.

FortiSOAR offers flexibility in deployment environments, including FortiSOAR Cloud, which is a subscription service that enables hosting on FortiCloud. This provides cloud-hosted management with scalable resources. Additionally, FortiSOAR supports deployment on VMware ESXi and Amazon Web Services (AWS), allowing organizations to choose based on their infrastructure preferences. This flexibility ensures that FortiSOAR can be integrated into various IT environments depending on business needs.