Small and medium business | Business Central, N...

Workflow User Group not completing after one approver approves

(5) Share

Report

Posted on by SP-29040942-0

269

Hi everyone,

I am using Dynamics 365 Business Central Online with the standard Workflow User Group functionality (no customizations).

My Workflow User Group is configured as follows:

Sequence 1: 2 approvers
Sequence 2: 7 approvers

My requirement is:

In Sequence 1, any one of the 2 approvers should approve, and then the workflow should move to Sequence 2.
In Sequence 2, any one of the 7 approvers should approve, and the document should be fully approved/released.

My workflow conditions are:

An approval request is approved → Sequence No. = 1
An approval request is approved → Sequence No. = 2

However, after one approver in Sequence 2 approves, the remaining approval entries stay Open, and the document remains Pending Approval. It does not complete the workflow.

There is:

Only one workflow enabled.
No custom AL code.
No Power Automate.
Using the standard Workflow User Group response.
Business Central Online.

My questions are:

Does the standard Workflow User Group support the scenario where any one approver in the same sequence is enough to complete that approval level?
If yes, is there any additional workflow configuration required?
If not, is a customization required to cancel the remaining approval entries after the first approval?

Any guidance or suggestions would be greatly appreciated.

@YUN ZHU @a33ik @Gerardo Rentería García @OussamaSabbouhPlease help!!!

Thank you!

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Suggested answer

Mohana Yadav 61,248 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Please check this.

https://mohana-dynamicsnav.blogspot.com/2023/07/how-to-create-workflow-that-sends.html

Was this reply helpful? Yes No
SP-29040942-0 269 on at

Like (1)

Report
Copy link

Link copied!

Hi @Mohana Yadav,

Thank you for your response.

However, the issue still persists.

My Workflow User Group is configured as follows:

1. Sequence No. 1 – Multiple approvers

2. Sequence No. 2 – Multiple approvers

The behavior for Sequence No. 1 is working as expected. When any one approver approves, the workflow moves to the next sequence.

The issue occurs at Sequence No. 2. Once the workflow reaches Sequence No. 2, approval requests are sent to all approvers in that sequence, and the workflow remains pending until each approver acts on the request.

My requirement is:

1. Sequence No. 1: Any one approver should approve and move to the next sequence.

2. Sequence No. 2: Any one approver should approve, and the document should be fully approved/released.

Currently, after one approver in Sequence No. 2 approves, the workflow does not complete and continues waiting for the remaining approvers.

Could you please confirm whether the standard Workflow User Group functionality supports the following scenario?

For Sequence No. 01

For Sequence No. 02

Response for Sequence No. 2

Workflow User Group:

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 19,050 Super User 2026 Season 2 on at

Like (2)

Report
Copy link

Link copied!

Hello,

Yes, standard Workflow User Groups support this scenario: when multiple users have the same Sequence No., approval by any one of them should move the workflow to the next sequence. In your case, the issue is likely in the workflow conditions rather than the user group itself; I would use the standard logic based on Pending Approvals > 0 for continuing and Pending Approvals = 0 for completing/releasing the document, instead of manually filtering the approval events by Sequence No. If one approver in Sequence 2 approves and the other six entries remain Open, review the workflow steps/responses against a standard Microsoft workflow template before considering customization, because customization should not normally be required for this requirement.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Suggested answer

Mohana Yadav 61,248 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

I think you dont need "Send approval request for the record and create a notification" Response for Sequence No. 2

Was this reply helpful? Yes No
Manish Sharma 146 on at

Like (0)

Report
Copy link

Link copied!

Hi @SP-29040942-0

Sharing our experience, there is no standard structure to handle this kind of workflow, we have seen blogs and postings, everyone says you need to customise, or you need to create separate workflow for multiple sequence and configure the sequence accordingly, some suggest using power automate.

Was this reply helpful? Yes No
Suggested answer

Tony NAVCore Develo... 14 on at

Like (0)

Report
Copy link

Link copied!

As stated by Mohana, you don't need the "Send approval request..." for your sequence no. 2. However, that event likely never ran because you have the condition Number of Approved Requests = 1. By this stage, you should have at least 2 approved requests already because sequence 1 must be approved before getting to sequence 2. Sequence 1 approved + sequence 2 approved = 2 or greater. Anyway, since you only need 1 person in sequence 2 to approve, then you can just remove that condition and your flow should work.

Was this reply helpful? Yes No
Suggested answer

Grigorios Mavrogeorgis 3,184 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi, standard does support this, no customization needed. The docs on workflow user groups say it plainly, when several users share the same Sequence No. only one of them has to approve and the workflow moves to the next step.
What I'd suspect is the two conditions you put on the approved event, Sequence No. = 1 and = 2. Take them out and run the plain template first. Those filters sit on the approval entry and can stop the release response from firing at all, then you get exactly what you describe, entry approved but document still pending.
Other thing to check, in the group all 7 must literally carry Sequence No. 2, not 2,3,4 and so on. And the approval entries are built at submit time, so a document already in flight keeps the old structure. Cancel it and resubmit after any change, otherwise you test the old setup.
Are all 7 really on sequence 2, or did they end up numbered one by one?

Glad to help - follow up if anything is unclear.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis

Was this reply helpful? Yes No