Support Article
Getting "No Flow name specified to start the processing" error
SA-34823
Summary
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.
Error Messages
No flow name specified to start the processing.
Steps to Reproduce
Not Applicable
Root Cause
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.
Resolution
Perform the following local-change:
Flow with draft mode on will not be picked in production environment, user can change the draft mode.
Published March 22, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.