Ask Search:
Carl MahCarl Mah 

flow version id

Hi I'm getting an error:

"Workflow Action Failed to Trigger Flow
The record couldn’t be saved because it failed to trigger a flow. 
A flow trigger failed to execute the flow with version ID 301L0000000DApe"

How do I find out which flow this version id corresponds to?
 
Best Answer chosen by Carl Mah
Jeff MayJeff May
Usually this means your Flow is not properly getting the record ID, and not properly handling situations where the Id, or one of the steps in the Flow, doesn't get the record or field value it is expecting.   

Here is a link that describes 1 way to debug Flows:  https://help.salesforce.com/apex/HTViewSolution?id=000187503&language=en_US (https://help.salesforce.com/apex/HTViewSolution?id=000187503&language=en_US)

All Answers

Mayank SrivastavaMayank Srivastava
Hey Carl,
Could you post a screenshot of your flow process configuration?
Carl MahCarl Mah
Hi Mayank 
Sorry can you be specific please - still new to this.
Jeff MayJeff May
Usually this means your Flow is not properly getting the record ID, and not properly handling situations where the Id, or one of the steps in the Flow, doesn't get the record or field value it is expecting.   

Here is a link that describes 1 way to debug Flows:  https://help.salesforce.com/apex/HTViewSolution?id=000187503&language=en_US (https://help.salesforce.com/apex/HTViewSolution?id=000187503&language=en_US)
This was selected as the best answer
Carl MahCarl Mah
Thanks Jeff - Ok now I know what these errors usually mean.
Now I can hopefully narrow down where in the flow exactly
 
Heather CreelHeather Creel
How to you determine which flow is causing the issue though? We have multiples running and I am not sure where to locate it by the ID referenced in the error. 
Jeff MayJeff May
If you turn on the Debug Log, there will be more info in the log including the Flow Name and usually extra error info.
Heather CreelHeather Creel
got it, thank you!
 
Stephen WoodStephen Wood
I am having this same issue, but the error occurs seldomly. I have tried to use the Debug Log, but I can never catch the error within the 24 hour period. Any advice on how to locate the Flow from the version ID?
Jeff MayJeff May
The error email conrtains the record IDs you can look at and try to manually do whatever the failed action was.

So, you can turn on Debug Log for your user (or yourself), and edit or change the record referenced in the email message. This will put the needed info in the Debug Log.
Dakota WalkerDakota Walker
A quick way to find the flow that is causing your error is to
1. Open the Flow Designer
2. Click "close" on the welcome screen-pop
3. Add the following to the end of your URL ...salesforce.com/designer/designer.apexp#Id=YOURFLOWIDHERE
Peter BenderPeter Bender
Dakota Walker's suggestion is a good one (Thanks!). However, be aware that the ID may reference either a Flow or a Process. I recommend his steps, with further additions as noted below:

1. Open the Flow Designer.
2. Click "close" on the welcome screen-pop (if it appears).
3. Add the following to the end of your URL and reload the page: ...salesforce.com/designer/designer.apexp#Id=YOURFLOWIDHERE
4. Note the name of the flow that appears that the top of the screen. Being cautious, Do not edit the flow here. Processes and Flows are built with the same technology, and this hack/method will pull up either one in the Flow editor. This is very handy, however editing a Process in this screen is likely to have bad unintended consequences.
5. Immediately exit the designer screen.
6. Now you will be either in the Process Builder list page or the page defining a specific Visual Workflow / Flow. If you are in the Process Builder page, navigate to find the Process you noted and open it as usual. If you are on the Flow page, just click on the appropriate link to open the Flow again.
Benjamin BarniskisBenjamin Barniskis
You can also do this if you use Workbench:
Goto Workbench > Utilities > REST Explorer > Make a GET call with this path (/services/data/v37.0/tooling/sobjects/flow/{flowID})
Julie GleasonJulie Gleason
You can also plug the ID into a URL that will open the underlying flow, where you can see the name of the flow that is causing the error. 

https://[instance].salesforce.com/designer/designer.apexp#Id=[id]
Replace the [] with your instance and flow ID that is erroring

Example:
https://na1.salesforce.com/designer/designer.apexp#Id=301xxxxxxxxxxxx
Robert LindRobert Lind
Heres another way:  
Open Developer Console.
In Query Editor check Use Tooling API box (next to Execute button)
Run this query: select masterlabel from flow where id = '301xxxxxxxxxxxxxxx'  - for both flows and process builders.

For more details on what can be viewed see Force.com Tooling API document.
Richard BlakeRichard Blake
https://workbench.developerforce.com > Info > Metadata Types & Components
Select 'Flow'
Click 'Expand All'
Search for the ID
Julie GleasonJulie Gleason
Richard Blake > much better solution. Thank you! 
Jerad MeidingerJerad Meidinger
Thanks for the help, folks. Here's what I did:
1. Open the Flow Designer
2. Open one of the flows you have.
3. Copy the Flow ID that has been causing problems.
4. REPLACE the last digits of the URL with your ID. ...salesforce.com/designer/designer.apexp#Id=YOURFLOWIDHERE
5. Hit Enter and wait for page to load. It will still have the original Flow Name.
6. Hit Ctrl + F5 for a hard refresh.
7. This new page will have the name of the Flow/Process Builder in the top left of the page.
8. Smile, repeatedly press fingertips together.
 
Smriti KumariSmriti Kumari
Another alternative way is using developer console and Tooling API.
Goto developer console -> query editor -> check use tooling api -> execute query: select fullname,Id,Description from flow where id = '301...' -> This way you can find the flow easily.