Flow Approvals Scrolling Issue

[jhenkel]

I have started using Approvals in in my Flows and PowerApps. Unfortunately, I have encountered an issue where, after clicking "approve" or "reject" in the email, the slide-out screen in the browser does not properly scroll, so the "confirm" button does not appear to the user. I first noticed the isse on a mobile device, but this morning a user reported the same issue on a Windows laptop. Is this a known bug? Is there a fix in the works?

[v-bacao-msft]

Hi @jhenkel,

Could you provide a specific screenshot?

I am not sure where you are completing the approval request.

I did a test on my side and approved it in the emails I received in O365 Outlook(web page) and in Flow mobile app. When I click on Approve/Reject, the Submit button is displayed normally.

Web page test results:

Mobile app test results:

Please provide more details so that we can do more tests.

Best Regards,

Barry

[Jambo1]

We have the same problem - it seems to be ok using Chrome, but in edge for example the approve button hides behind the taskbar and makes it tricky to click - see below

[jhenkel]

Thanks for the reply. I should have mentioned that I have about 12 lines in the approval detail. I tried to limit the amount of text as best I could, but I am dealing with a large userbase that benefits from detailed instructions; even if it is to say: "Don't forget to hit confirm..." :D. I appreciate the help.

The iOS experience is particularly bad. Initially the left side menu covers the approval. After you hide the menu, you need to click approve again, and even then, you can't scroll all the way down. I think the Windows issue is with Edge. When I get back to my Windows 10 machine, I will grab a screenshot from there as well.

Here is a screenshot on Safari in iOS:

[jhenkel]

Here is the screenshot from Edge on Windows 10. The issue is happend when the details text pushes the confirm button beyond the size of the window. Here is the screenshot:

[dmclaughlin]

I'm having same issue in google, the approver cant scroll to get to the area to click approve or reject.  The scroll bar is not there.  Is this a setting?  Most pc's have been fine but this one is not.

[Anonymous]

Having a similar issue.  Per our internal requirements, the "Details" text is more extensive than allowable within screen frame without "Zooming out" to 60-70% to see everything.  Just a few weeks ago, a scroll-bar was present to allow full view of all text and approval button as well as "commentary" box.  Is this a browser issue (found in both Edge and Chrome) or is this a Power Automate issue? @v-yutliu-msft , @mdevaney , @v-bacao-msft 

[mdevaney]

@Anonymous 

Why did you mention me in this post, lol? 

[dmclaughlin]

sorry.. I thought I saw you having the same issues. 

[Anonymous]

I am also having this issue!!!

This worked yesterday for the flows that contain authorisation steps however today it does not! My authorsiation steps do contain a lot of dynamic detail/text, however they have been running without issue for about 9months, and when run by the same user on the same PC or different PC in both explorer or chrome the functionality to scroll to the bottom/display the text box has vanished.

[Anonymous]

As you can see the confirm button is "Greyed" out and there is no functionality to scroll to the bottom or choose the appropriate response/add comments.

[Anonymous]

I too am having this issue. It's quite unfortunate because every other aspect of the approvals process in Power Automate is seemless. This has to be a simple fix on their end to add a scroll bar..

Hoping this will gain attention and be resolved asap.

[stevegeall]

Same issue here (18th Feb 2020) - posting so I get alerted of any updates 🙂

[Mhak]

Same issue with me. Had to reassign through the mobile app because the browser is not playing ball since last Friday. 

[GavinMc]

I know this is not a fix, but if you change the browser zoom level, you will eventually get to see all the buttons and info of the approval. Temporary option until the proper fix is found.

[kaband]

FYI - I have a ticket opened with Microsoft.  I'm not the only one who has opened a ticket regarding this issue and did hear back that an internal ticket has been opened with the Product Group.

[Mhak]

Yeah, I figured that out as well, but yeah, that is not how it is meant to work...Just imagine having to reassign and scroll through some names..not ideal at all. But thank you. 🙂