Workflow error: "The workflow was automatically rejected by the system. Alternate final approval was required, but no approver was found."

(0) Share

Report

Posted on by Community Member

Hi!

We are setting up Workflow in GP 2015 R2. I have tried setting up a Financial GL Batch Workflow and a Vendor Setup Workflow and in both cases, when we click "Submit" and check the Workflow, we receive the error: "The workflow was automatically rejected by the system. Alternate final approval was required, but no approver was found."

I have tried setting up very simple workflows with originator being the approver and with and without additional approvers and keep getting the same error. I have run the exec wfDeployClrAssemblies Stored Procedure on our Dynamics database but it hasn't helped. All of the Managers and User Names are pulling correctly from Active Directory.

Looking for other items to check.

Thank you!

Karl Stadick

Financial Systems Administrator

Hub Group Dedicated

Mesa, AZ

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Andrea Melroe 3,437 on at

Like (0)

Report

RE: Workflow error: "The workflow was automatically rejected by the system. Alternate final approval was required, but no approver was found."

Hi Karl,

First, I recommend you unmark ‘Always require at least one approver’ in the Workflow Maintenance window to see it that makes a difference. Depending on the setup, the workflow may be trying to assign a task to an Alternate Approver when none is assigned.

If that doesn’t make a difference: I’ve also seen this type of error caused by the SQL Service being run with a local user account and therefore not being able to query Active Directory to verify the Workflow Users. In those instances, the users had to switch the SQL Service(s) to run with a Domain Service Account instead that has access to your domain or domains.

I hope this helps!

Andrea Melroe | Sr. Technical Advisor | Microsoft Dynamics GP

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

RE: Workflow error: "The workflow was automatically rejected by the system. Alternate final approval was required, but no approver was found."

Hi.

I had the same issues described but my resolution was slightly different. it turned out that my SQL Services user had been locked out of AD. When the user was unlocking then the workflow started working again.

Thank you

Neil Palmer

Was this reply helpful? Yes No
Derek Albaugh on at

Like (0)

Report

RE: Workflow error: "The workflow was automatically rejected by the system. Alternate final approval was required, but no approver was found."

To add to this, the SQL Server service account is used by Workflow in some processing, to query the Active Directory to determine whether assigned approvers, alternate final approvers and workflow managers are valid accounts or not. If the SQL service account can't query the AD for whatever reason, Workflow will automatically reject the workflows, which, if the workflow is setup to require at least one approver, it'll then try to route the workflow to any specified alternate final approver and if one isn't specified, the workflow manager.

However, if it can't verify any of these accounts in AD, it'll throw the type of error message you were seeing, which is why unlocking the SQL services account resolved the issue.

Thanks

Was this reply helpful? Yes No