Querying, reporting, and governing Process Instance Nodes

Working with Process Instance Nodes is mostly a reporting and audit activity, not a configuration one. The platform creates and updates the records automatically as Approval Processes run. The four-piece routine for the admin who owns approval governance covers: query Process Instance Nodes for current state, build standard reports on the object, monitor for stuck nodes that need intervention, and plan migration of legacy Approval Processes to Flow Orchestration when ready. Each piece is independent and can be adopted at the pace the team chooses.

1. 1
   Query Process Instance Nodes for current state

   From Developer Console or Workbench, run a SOQL query against ProcessInstanceNode to see the current state of approvals. SELECT Id, Status, ProcessInstanceId, NodeApproverId, CompletedDate FROM ProcessInstanceNode WHERE Status = Pending shows everything currently waiting. Filter by ProcessInstance.TargetObjectId to drill into a specific record. Filter by NodeApproverId to see what an individual approver is sitting on. Use this query pattern as the basis for any custom report, dashboard, or escalation logic. Document the canonical query patterns in your approval governance runbook so other admins do not invent slightly different versions.

2. 2
   Build standard reports on the ProcessInstanceNode object

   Create a Custom Report Type that joins ProcessInstanceNode, ProcessInstance, and the related record object (Opportunity, Case, custom object) through the TargetObjectId. Build the core reports: Pending Approvals by Approver (who is sitting on what), Average Time to Approve by Process (which processes are slow), Rejection Rate by Process (which processes get rejected most often), Recalled Approvals by Submitter (who is recalling and why). Add the reports to an Approval Governance dashboard. Schedule the dashboard to email approval owners weekly so process problems surface without manual digging.

3. 3
   Monitor for stuck nodes and intervene

   Build a dashboard alert (or Flow trigger) that flags any ProcessInstanceNode in Pending status for more than the configured SLA (typically 3 to 5 business days). For each stuck node, the alert should identify the approver, the request, and the elapsed time. Route the alert to the process owner or to a designated triage queue. The process owner can reassign the node to a backup approver, escalate to the manager, or recall the request for revision. Without active monitoring, stuck approvals quietly age and submit users learn to avoid the process entirely. Treat stuck-node intervention as part of approval governance, not as an emergency response.

4. 4
   Plan migration to Flow Orchestration when ready

   For each Approval Process in production, evaluate whether migration to Flow Orchestration adds value. Flow Orchestration provides richer step types (subflows, screen interactions, decision branches), better visual design, and Salesforce ongoing investment. Migration is a manual rebuild (no automated tool exists), so prioritize processes that gain the most from the new features. Document each rebuild in the org automation registry. Run both the old and new approval processes in parallel during a transition window so production work is not disrupted. Decommission the old Approval Process once the new Orchestration has been stable for a quarter.