Troubleshooting Tip: Health check and Block IP action fail after upgrading FortiGate connector to 5.4.0 version

[jankit6]

Description	This article describes how to resolve an issue that occurs after upgrading the FortiGate connector to version 5.4.0.
Scope	FortiSOAR and FortiGate Connector version 5.4.0
Solution	Issue 1:   After upgrading the FortiGate connector to the 5.4.0 version, the health check might fail with the following error. Reason for failure: Starting from FortiGate connector version 5.4.0, the health check validates the Profile name whether it exists or not. If the profile name is configured in the connector and does not exist in FortiGate, the health check will fail. Resolution step: Either create the same profile in ForitGate or remove its entry from FortiGate connector configuration in FortiSOAR Issue 2: Block IP action does not block the IP in FortiGate If the address group created to block/unblock an IP is not included in the firewall policy, this issue may occur. Ensure that the address group is added to the appropriate firewall policy. Related article:  Basic category filters and overrides - FortiGate administration guide