Getting "No Flow name specified to start the processing" error
User is getting a "No Flow name specified to start the processing" in the production application.
However the flow exists and this did not happen in earlier environments.
No flow name specified to start the processing.
Steps to Reproduce
An issue in the custom application code or rules.
User has just moved to production and they have moved a flow with draft mode on to prod and that's the reason they are facing the error.
Perform the following local-change:
Flow with draft mode on will not be picked in production environment, user can change the draft mode.
20% found this useful