Hello,
Scenario:
- 1 separated environment (not default)
- 1 solution with several flows, environment variables and connection references
- 1 of the flows included in my solution uses multiple "start and wait for approval" actions (in parallel branches for different users). This flow already sent plenty of approvals to different users.
- Worked fine for some months but now one instance (yes, only 1 instance) stucks on one "start and wait for approval" action
- The specified user email is correct, user is already added to Dataverse Environment with role "Approval User", also the user received some approvals before yesterday and also received some today
- I ensured "Send notification" in the appropriate action is set to Yes
Problem:
- The user did not receive any approval - not only email or teams message is missing, also approval itself is missing/not created
(checked here https://emea.flow.microsoft.com/manage/environments/{EnvironmentId}/approvals/sent)
- Flow stucks now on "Start and wait for approval" since 18 hours.
Question:
Anyone else also faced the issue that suddenly, for obviously no reason an approval has not been created (but others for the same user used to work and also at the same time some approvals has been created for other users)?
Is there any way to "solve" this issue or do i have to declare that as a bug and have to hope this does not happen again?
Thanks for any assistance.
I had a similar problem this morning. Approval flow has been working fine as recently as yesterday. Approval ran this morning, staff member approved a request; however, the flow stalled out at the wait for approval step. After an hour of running, the flow just canceled, even though the request was approved. Not sure what changed between yesterday and today. Tried to resubmit and same thing occurred.
WarrenBelz
146,631
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
65,991
Most Valuable Professional