Error deploying mdapi flows to packaging org
As the error says, you need to contact Support. Once any file has an error of the Internal Server Error variety, all remaining files will also have that same error. There really is (most likely) only one broken flow in the bunch; you might try deploying them one at a time to find the offending file. I can ask my contacts to tell me what the error maps to, but without your file, there's little hope of telling you specifically what's wrong with your file. Again, to be clear, you need to contact Support to get this cleared up.
Here's what I've learned through trial and error:
1) I am unable to deploy my flows to a partner dev org that already has a namespace, as reported in my post here yesterday.
2) I am able to deploy to a partner dev org with no namespace. The links to platform events are intact when deployed. However....
3) When you set a namespace on that org, it breaks the links to the platform events.
4) When I repaired the links to the platform events and tried to save the flows, I got the error message. I just Shift-Command-M to open the message window in flows, I was able to determine that a number of other custom fields in custom objects were inaccessible by the flows. I had to adjust field level security for a number of the custom fields in the custom objects to make them visible to the flow. I don't understand this because the flows are run by the system, not by users or admins, so I would expect the system to be able to see these fields, regardless of field-level security. When all the troublesome fields were repaired, I was able to save the flows.
Summary: namespace appears to break some, but not all, links to custom fields and custom objects (including platform events) in flows. SFDX cannot deploy when these errors are present.
Workaround: deploy to non-namespaced org, add namespace, repair flows, move on. Not ideal, but I can move forward.
UPDATE: thx sfdcfox for the comment about perm set when editing the flows. I tested, and you're exactly right.
In my previous post, I reported that Flows lose connection to the Platform Event parameters and to some custom fields in custom objects. I can now clarify.
As previously reported, the flows will not deploy to a namespaced dev org. I can deploy to a non-namespaced dev org, and then subsequently add the namespace. When the namespace is added, the links to the Platform Event parameters are lost.
I had incorrectly assumed that the Platform Event links issue and the broken links to custom fields/custom objects were related, and caused by the namespace.
The issue I was having with the missing custom fields turns out NOT to be related to namespace, but to the fact that when I was editing the flows and resaving them, I had not assigned myself the permission set needed to access the custom fields. This is really strange, as the flows are run at a system level, not by a user, so I wouldn't expect the perm set to matter -- but it does, apparently.
So, current workflow needs to be:
- deploy mdapi with flows to non-namespaced org
- assign the necessary perm set to access custom objects/fields
- apply the namespace
- edit the flows to re-establish the links to platform events