Chain account integrations via queueables#2
Draft
Paritoshkumar148 wants to merge 1 commit into
Draft
Conversation
…ove sync processing Co-authored-by: kumarparitosh148 <kumarparitosh148@gmail.com>
|
Cursor Agent can help with this pull request. Just |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Consolidate chained Queueable jobs and refactor child account processing to prevent "too many queueable jobs" errors.
The previous implementation created multiple chained Queueable jobs per account, and then recursively created more for each child account via a batch, quickly exceeding Salesforce's 50 Queueable jobs per transaction limit. This PR consolidates all integrations into a single Queueable job and processes child accounts synchronously or via a batch that calls synchronous methods, ensuring compliance with governor limits.