Flows · Practical investigation guide
Which Salesforce flow version is active?
A newer version can exist alongside a different active version. Compare what the exports say before concluding why the flow behaves differently.
Open the flow-version investigation →Follow the evidence
- Identify the flow. Use its API developer name. The fictional example uses Account_Before_Save; replace it with your selected flow when running real queries.
- Query its definition. Open the flow-version workspace. Run the definition query through the Tooling API. Import its complete export to unlock the version list when one definition matches.
- Review version history. Run the displayed versions query. Examine version numbers, statuses, API versions and modification details in the supplied rows.
- Compare equivalent exports. Enable comparison when you have another export from the corresponding flow. Use equivalent parameters and capture times. Review active/latest numbers and declared version comparison columns.
Try it first
Choose “Try fictional sample” to inspect a complete example. For a guided comparison, follow the five-minute walkthrough.
Five-minute fictional walkthrough →What this does not establish
Matching version numbers or statuses do not prove matching flow logic. These queries do not show the full flow definition or verify actual runtime execution.
Continue your investigation
Flows associated with an object · Choose another starting point
Work from authorised exports. Browser analysis stays in the current tab; downloaded reports remain on your device.