Apex Code Development You need to sign in to do that
Don't have an account?
Some Flows not Available to Include in Package
Hello everyone,
I am working on an unmanaged package that will eventually become managed. When I try to add flows to the package, I have noticed that some of them do not show up in the list under Flow Definitions. I have looked around online but have not been able to find anything about why some flows would show up to be included but others would not. I have verified that the flows that I want to add are active and not already included in the package.
Why might this happen, and can it be fixed? Are there certain actions a flow can take that disqualify it from being packaged? Is there anything else that is vital to know about dealing with flows in packages other than that new versions cannot be included in patches?
I am working on an unmanaged package that will eventually become managed. When I try to add flows to the package, I have noticed that some of them do not show up in the list under Flow Definitions. I have looked around online but have not been able to find anything about why some flows would show up to be included but others would not. I have verified that the flows that I want to add are active and not already included in the package.
Why might this happen, and can it be fixed? Are there certain actions a flow can take that disqualify it from being packaged? Is there anything else that is vital to know about dealing with flows in packages other than that new versions cannot be included in patches?
https://help.salesforce.com/s/articleView?id=sf.flow_considerations_distribute_package.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.flow_considerations_manage_install.htm&type=5
Hope above information was helpful.
Please mark as Best Answer so that it can help others in the future.
Thanks,
All Answers
https://help.salesforce.com/s/articleView?id=sf.flow_considerations_distribute_package.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.flow_considerations_manage_install.htm&type=5
Hope above information was helpful.
Please mark as Best Answer so that it can help others in the future.
Thanks,
This ended up being a naming issue. It turns out that Flows can have different names than their flow versions. I was looking for the flow name, but the flow version name was the one that showes up in the list for packaging. All is well.