Community
User Guides
Support
Community
Help Forums
English Forum
General
About our Community
General Discussion
News and Feedback
Products
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Beta programs
Feature Requests
Finnish Forum (Tukifoorumi)
Tuotteet Kotiin
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Muut tietoturvatuotteet
Support Articles
Language
English
Suomi
Deutsch
Français
日本語
Svenska
Dansk
Italiano
Nederlands
Norsk
Polski
中文 (繁體)
Products & Services
F-Secure TOTAL
F-Secure SAFE / Internet Security / Anti-Virus
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Common topics
User Guides
Support
Login
|
Register
Error output of "System.LimitException: AFSC:Too many queueable jobs added to the queue: 2 (AFSC)" when using F-Secure Cloud Protection for Salesforce - F-Secure Community
<main> <article class="userContent"> <h3 data-version="5" data-article="000010629" data-id="issue">Issue:</h3> <p>I noticed that the following error message is output when a queueable job that adds date field values to related cases on "Case Status Update" is triggered.<br>This job always starts a new job in the queueable context. Somehow, F-Secure Cloud Protection for Salesforce starts another job in the same context, which leads to the error message.<br><br><b>Error message:</b><br>FATAL_ERROR|System.LimitException: AFSC:Too many queueable jobs added to the queue: 2 (AFSC)</p> <h3 data-id="resolution">Resolution:</h3> <p>If you are using an older version of F-Secure Cloud Protection for Salesforce, proceed to upgrade the application to the latest version and check if there is any improvement.<br><br>If the issue persists, proceed to report the issue by contacting <a rel="nofollow" href="http://www.f-secure.com/en/web/business_global/support/support-request#productGroup=For%20Business">F-Secure Support</a>. In order for us to collect the debug logs and investigate the issue further at our end, you need to:<br></p><ul><li>Allow us the remote login access to your Salesforce organization</li><li>Provide us with detail instructions on how to reproduce the issue</li></ul><p>Article no: 000010629</p> </article> </main>