Org Process Graph

When three Flows, a trigger, and two workflow rules all fire on the same object, the order they run in decides the outcome — and almost no one can recite that order from memory. Org Process Graph draws the whole picture: every automation on an object, how it is wired, and where it conflicts.

The dependency graph

Org Process Graph renders all automation on an object as an interactive graph:

  • record-triggered and scheduled Flows
  • Apex triggers
  • Workflow rules
  • Validation rules
  • approval processes

Edges show what triggers what, so you can follow a save event through the entire chain instead of imagining it.

Execution order

The graph models Salesforce's order of execution, so you can see the sequence automations actually run in — before-save vs after-save, triggers vs flows vs workflow. This is where order-of-operations bugs hide: a before-save flow that sets a field, overwritten by an after-save trigger, producing a result that looks impossible until you see the order on screen.

Conflict and dead-code detection

Org Process Graph flags the problems that cause the hardest automation bugs:

  • Dead automation — Flows or rules that are inactive, or that can never be reached. Clutter that makes the real logic harder to find.
  • Duplicate writers — multiple automations writing the same field. The classic source of "this field keeps changing and I do not know why."
  • Object health scoring — a per-object signal for how tangled its automation has become.

Removal simulation

Before you deactivate or delete an automation, run a removal simulation: Org Process Graph shows what depends on it and what would break. "What happens if I delete this old workflow?" gets a real answer instead of a held breath.

Documentation export

Export the graph as Mermaid to drop a current, accurate automation diagram straight into your runbooks or a pull request — documentation that matches the org because it was generated from it.

Related reading