We want to notify you of an important Critical Update (CRUC) that will impact how records are routed through the right Approval Process when submitted behind the scenes (Process Builder, a Flow or API call). We recommend that you review any customizations that submit records for approval behind the scenes before the CRUC auto activates on April 2, 2019. This will ensure that records are submitted to the correct approval process.
Previously, when you submitted a record behind the scenes, whether through Process Builder, a Flow, or API call , Salesforce picked the first approval process where the record met the entry criteria. It didn’t check whether the user submitting the record (or the user-supplied via submitter ID) was an allowed submitter.
When this CRUC auto activates on April 2, 2019, and a customization (such as an Apex class or a process) submits a record for approval, Salesforce will pick the first approval process where the record meets the entry criteria and the submitter ID is an allowed submitter. If the submitter ID is not allowed, the following error message will be displayed: "No applicable approval process was found."
Review any customizations you have implemented that submit a record for approval behind the scenes well before April 2, 2019. We recommend you use the CRUC setting to test their behavior in a Sandbox for potential impact. For example, each approval process that the customization can invoke, update the list of allowed submitters to include whichever users’ ID could be used to submit the record. For additional guidance, read the release notes.
If you have further questions, please reach out to Support by opening a case via Salesforce Help.