F-Secure is using Future Method to run scans and clashes with custom scripts that also uses Future Method. Any suggestions on how to resolve this?
By default Cloud Protection for SalesForce uses Queueable Jobs for invoking email attachment scan. However if Future Method was called, this means that the limits of Queueable jobs has been reached so F-Secure App switches to using Future Method instead. It is not possible to call Future Method from a Future Method as they are asynchronous.
We suggest to use the Queueable interface instead of a Future Method for custom scripts. The Queueable interface allows chain jobs, meaning F-Secure job could be started without the system exception from custom jobs.
Article no: 000031101