Finding guide

Multiple flows and triggers on the same object

Stacked automation is two or more flows, Apex triggers or workflow rules that fire on the same object at the same moment, for example after an Opportunity is updated. Salesforce runs them in a fixed sequence by type, but within a type the order is only as predictable as you made it. Each one added makes changes slower to test and easier to break.

By VanguardOps, written by a Salesforce architect with 13+ years in enterprise orgs. Updated November 17, 2026.

Why it matters

  • Two automations can update the same field and the last one wins, so a record ends up with a value nobody intended.
  • One automation's update can fire another, which can loop until a governor limit stops the save.
  • Every extra automation on a busy object costs CPU time and queries on every save, including bulk loads and integrations.
  • An Agentforce agent that updates a record sets all of it off, so the agent inherits the tangle.

How to check your org by hand

  1. In Setup, open Object Manager, pick the object, and open Flow Triggers to see its record-triggered flows by timing.
  2. On the same object, open Triggers to list its Apex triggers.
  3. In Setup, open Workflow Rules and filter to the object to find active rules.
  4. Write down, for create and for update, everything that fires before save and after save. Any slot with two or more is stacked.

How to fix it

  1. Aim for one before-save flow and one after-save flow per object, or one trigger with a handler class if the object is code-heavy.
  2. Move workflow rules and Process Builder logic into those flows rather than adding new ones beside them.
  3. Where several flows must stay, set their trigger order in Flow Trigger Explorer so the order is explicit.
  4. Test with bulk updates, not one record at a time. Stacking problems show up under load.

What VanguardOps flags

A scan checks this from metadata with fixed rules, never by reading records:

  • Record-triggered flows, Apex triggers and active workflow rules, grouped by object, operation (create, update, delete) and timing (before or after save).
  • Two automations in one slot is a low finding, three is medium, four or more is high.
  • Each finding names the object, the event and every automation in it.

Common questions

Can you have more than one record-triggered flow on an object?
Yes. Salesforce allows several, and you can set their order in Flow Trigger Explorer. The problem isn't that it's allowed; it's that each one added makes the object harder to change safely.
In what order do flows, triggers and workflow rules run?
Salesforce follows a fixed order of execution: before-save flows, then before triggers, then validation, then after triggers, then workflow rules and processes, then after-save flows. Within the same type the order is only set if you set it. Check Salesforce's order of execution documentation for the current detail.
Should I use one flow per object?
One before-save and one after-save flow per object is a sensible default. Some teams split by purpose with clear entry conditions and a set trigger order. What matters is that someone can read the full list for an object in a minute.