The documentation is stating
I have a flow that uses 'start and wait for an approval'. The approval timeout is set to 1 hour.
But when it goes into timeout, the approval request is not removed and also not giving an error in the approvals center.
Is the 30 days timout behaviour as described in the documentation different from when a manual timout is set?
Thank you for your feedback!
I have tested on my side that creates an Approval Flow with timeout limit, wait for it goes into timeout, the approval center will still have the approval request and I still could approve it, however, the status of the Approval request in Common Data Center will change into Inactive and the Flow will fail.
Approval request in Common Data Center:
Flow time out:
You can go to the end of this document, send feedback about this page, it will be taken care of it as soon as possible.
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for this information and the confirmation.
I have reviewed the CDS records (msdyn_flow_approvals and msdyn_flow_approvalrequests) for my testcases and can't find the "Inactive" status. Nothing changes to these records after the timeout.
Timed-out approvals are NOT removed nor is a error indicated when acting on a Timed-out approval from the record center.
This may be more of a feature request but, emails do not generate an error when approving timed-out approvals from an approval email. This is not outlined in documentation but I would hope this would occur as the current functionality make it seem that the user is completing an approval process from the generated email.
Not sure why this is not a big deal as requests just pile up in the Approval Center. Makes the Approval Center unusable.
This is simple to confirm. Create a flow add "Start and wait for an approval" change the "Timeout" to 30 second (PT30S). Add a scope with the "Configure run after" to "has timed out" then add another approval within the scope and repeat an one or twor times. Run the flow against an item , in my case I have used a I have used a Sharepoint Document Library. Run the flow and you will see that all the approvals stack up and remain in the Approval Center. If you select them in any order you can act on them without error.
If I am configuring my flow incorrectly please let me know.
Please confirm this is either A Bug or Not A Bug and if not update the documentation as necessary to reflect correct functionality.
are there new informations about this bug?
We are experiencing it too and it makes the reassignment feature almost impossible to use because the approver does not know which approval process timed out and which did not. We need a fix or some kind of workaround.
I have this problem too. I can't find any reasonable correction for it.
If you view the approval in the CDS, the expiration is set to end of 9999 rather than the timeout specified in the creation of the approval.
The only workaround I can think of is to ensure the requestor for each approval is a service account and then sign in as the service account to remove the no longer relevant approvals. This is less than ideal.
I have this issue too and it is frustrating for managers and leaders who can't approve the requests and I have to step in and manually approve or remove timed out approval requests, which defeats the whole purpose of Power Automate...
When will this bug be fixed?
The approvals are created in CDS in the table Approvals. You can delete or change the status of the approval on time out to clear the approval requests.
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!
Check out the community blog page where you can find valuable learning material from community and product team members!