Related Posts
Cover letter = Beg for this job.
I’m not doing it
Additional Posts in Salesforce Professionals
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
Cover letter = Beg for this job.
I’m not doing it
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Download the Fishbowl app to unlock all discussions on Fishbowl.
Copy and paste embed code on your site

Scan your QR code to download
Fishbowl app on your mobile

Subject Expert
https://architect.salesforce.com/decision-guides/trigger-automation
Typically one before flow (fast field updates) and one after flow. Triggers should be avoided to the extent possible. If unavoidable - 1 trigger per object.
Relevant quote:
“When it came to building automation in Process Builder, performance was a big reason to recommend building one process per object/trigger. Process Builder has a high initialization cost, so every time a Process Builder ran on a record edit, it would incur a performance hit, and since Process Builder didn’t come with any gating entry conditions, those hits would always be incurred on every edit. Flow functions differently than Process Builder, so it does not have nearly as high of an initialization cost, but it does have some.”