Custom Approvals: Comments not passing through when entered from Outlook client

I recently came back to a Flow I have been developing and noticed that my comments - using the "Start and wait for an approval (V2)" connector with the Custom responses option - are returning as "{{comments[custom response label].value}}" instead of the string value that is passed into the comments box. This behavior is observed when the user responds to the approval request using the Outlook email client (version 1808).

Example of returned data from the approval connector when the Outlook email client is used:

Example when using Outlook Online (through a browser window) is used:

I have tried converting the comments to a string value in my Flow; however, I still get the same result when using the Outlook client.

Re: Custom Approvals: Comments not passing through when entered from Outlook client

I updated my version of the Outlook for O365 client to version 1905 (Build 11629.20214) and still experience the same issue.

I can confirm that it works when logging into my Flow account, but it seems pointless to prompt users to respond to the request by selecting "Show original message" at the bottom of the request email and ignore the entirety of the approval email. Why even have this functionality (responding in the email) if users still have to log in and respond to the request the old way?

My question then: since this feature was working last week with my previous version of Outlook and now it isn't, does it not seem more likely that a change was made to Flow that is now causing the compatibility issues with the Outlook email client?

Re: Custom Approvals: Comments not passing through when entered from Outlook client

No, that is definitely not a solution, it is at best a workaround until a fix can be implemented. I believe this to be a bug, please escalate it to the product team for resolution.

There is no indicator to the end user that there is an issue with the comment field, it looks like it works fine from their perspective. So the data they enter is lost, and cannot be recorded into SharePoint, etc. Which makes this Premium Approval workflow basically useless, but we are charged for it as Plan 1.