Runtime Governance
Identify idle iFlows, orphaned artifacts, and potential duplicates across your tenant.
Pro+ only: Runtime Governance requires a Professional or Enterprise license.
Overview
As CPI tenants grow, technical debt accumulates: iFlows that are deployed but never process messages, artifacts deployed without design-time sources, and near-duplicate iFlows created by different teams. The Governance section in the Dashboard tab helps you find and clean up these issues.
Accessing Governance
Scroll to the bottom of the Dashboard tab to find the Runtime Governance panel. Select a lookback period (7, 14, 30, or 60 days) and click ↻ Analyze to scan your tenant.
Performance note: Governance data is cached server-side for 120 seconds. The scan uses bulk API calls (not per-package loops) so it works efficiently even on tenants with 1,000+ iFlows.
Idle iFlows
An iFlow is considered idle if it is deployed and started but has not processed any messages within the selected lookback period. Common causes:
- Test iFlows left running after development
- Deprecated integrations that were never undeployed
- Timer-based iFlows whose schedules are set far in the future
The idle list shows each iFlow's name, deployment date, and last message timestamp (if any). Use this to decide whether to undeploy or investigate further.
Ghosted Artifacts
A ghosted artifact is an iFlow that exists in the runtime (deployed) but has no corresponding design-time artifact. This can happen when:
- The design-time package was deleted but the runtime was not cleaned up
- An iFlow was deployed from a different tenant or via API and the source was never saved
- A failed undeploy left the runtime artifact behind
Ghosted artifacts are risky because they cannot be edited, versioned, or redeployed through the normal workflow.
Potential Duplicates
The duplicate detector compares iFlow names using similarity matching. It groups iFlows whose names are nearly identical (e.g., Order_Sync_v1 and Order_Sync_v2, or CustomerReplication and Customer_Replication).
Each group shows the matching iFlow names. This is a heuristic — not every match is a real duplicate, but it surfaces candidates worth investigating.
Stat Cards
After the scan completes, three stat cards summarise the results:
| Card | Shows |
|---|---|
| Idle iFlows | Count of deployed iFlows with no recent message activity |
| Ghosted | Count of runtime artifacts missing a design-time source |
| Duplicate Groups | Number of groups of potentially duplicated iFlow names |
Best Practices
- Run a governance scan at least once a month to keep your tenant clean
- Undeploy idle iFlows that are no longer needed — they consume runtime memory
- Investigate ghosted artifacts and either recreate the design-time source or undeploy the runtime
- Review duplicate groups with your team to consolidate or rename iFlows