Execution Graph Viewer
The Execution Graph Viewer provides a visual map of how triggers, flows, and other automations execute for a given Salesforce object. It displays entry points, execution phases, edges representing execution flow, and rule nodes showing what each automation does. It is available on Enterprise plans only and is currently in BETA.
What the Graph Shows
Salesforce executes automations in a specific order when a record is created, updated, or deleted. The Execution Graph makes this order visible by displaying:
- Entry points -- the DML events that initiate execution (e.g., INSERT, UPDATE, DELETE).
- Execution phases -- before-save flows, validation rules, before triggers, after triggers, after-save flows, and other phases in the Salesforce execution order.
- Edges -- directed connections showing the flow from one execution step to the next.
- Rule nodes -- individual automations (triggers, flows, validation rules, process builders) placed within their execution phase.
Reading the Graph
Entry Points
Entry points appear on the left side of the graph. Each entry point represents a DML event type:
- INSERT -- record creation.
- UPDATE -- record modification.
- DELETE -- record deletion.
- Compound events -- some triggers fire on multiple events (e.g., INSERT and UPDATE). These appear as a single entry point labeled with all applicable events.
Execution Phases
The graph is organized from left to right following the Salesforce order of execution. Nodes are grouped by phase, making it clear which automations run before or after others.
Rule Nodes
Each rule node displays:
- Name -- the automation's API name.
- Type -- the kind of automation (Trigger, Flow, Validation Rule, etc.), indicated by a color-coded badge.
- Business label -- the AI-generated description of what the automation does.
Click a rule node to view its full documentation, including business rules, evidence, and affected fields.
The graph is especially valuable for troubleshooting execution order issues. If a trigger and a flow both modify the same field, the graph shows which runs first.
Navigation
Pan and Zoom
- Pan -- click and drag the background to move around the graph.
- Zoom -- use the scroll wheel or pinch gesture to zoom in and out.
- Fit to view -- click the fit-to-view button in the toolbar to reset the zoom level so the entire graph is visible.
Layout
The graph uses an automatic layout algorithm that minimizes edge crossings and groups related nodes. For complex objects with many automations, the layout spreads nodes across multiple rows to maintain readability.
How to Access
The Execution Graph Viewer is a top-level tab in the aprity app sidebar:
- Open the aprity app in Salesforce.
- Click the Execution Graph tab in the sidebar navigation (marked with a BETA badge).
- The graph loads automatically for the currently selected scan.
The graph displays in an embedded iframe within the aprity app. It loads via a signed URL that authenticates the session. The iframe runs with restricted permissions (scripts, same-origin, and popups only).
The graph viewer requires a completed scan with analysis results. It is not available for scans that are still running or that failed before the analysis phase.
Technical Details
The graph is rendered using an interactive JavaScript library within an iframe. The signed URL includes an authentication token that expires after a limited time. If the token expires, close and reopen the graph to obtain a new signed URL.
The graph data is derived from aprity's deterministic dependency analysis, not from AI. The execution order and phase assignments are computed directly from Salesforce metadata.
The Execution Graph is deterministic. Running the same scan twice on the same org produces the same graph. There is no AI interpretation involved in the execution order -- only in the business labels assigned to rule nodes.
Limitations
- The graph shows the execution order for a single object at a time. Cross-object execution chains (e.g., a trigger on Account that updates Contact) are not displayed in a single graph.
- The graph reflects the automations present at the time of the scan. Real-time changes to your org are not reflected until a new scan is run.
- Very complex objects with dozens of automations may produce large graphs that require scrolling and zooming to review fully.
Plan Availability
| Plan | Execution Graph Available |
|---|---|
| Trial | No |
| Starter | No |
| Professional | No |
| Enterprise | Yes |