Unanswered

Endpoint Error with Approval Request

(2) Share

Report

Posted on by MV-04061936-0

Hello,

I have built a flow which used to work and now I am running into a problem where when the some user receives the Approval Email, when they click on Approve or Reject, they get "The remote endpoint returned an error (HTTP '403'). Please try again later.

Here is more info:

The email address of the approver is stored into a variable since the flow processes data from an external system. The email address output variable is then entered in the assigned to field of teh Create an approval step.

The flow creater is called process.automation.

When I send the approval to my email address or a co-worker it works for us. However, some users get the error "The remote endpoint returned an error (HTTP '403'). Please try again later." in outlook. And when they use Outlook Web they get the error "Failed to validate the signature of the actionable message card."

I am at lost, I verified to make sure the email address they are signed in under in outlook is the same as their azure profile.

Any ideas would be greatly appreciated.

Thanks

Categories:

Building flows

I have the same question (2)

All responses (4)

Answers (0)

PPYY 10 on at

Like (0)

Report

Hi there, did you manage to find a solution? I have the same issues. At first i thought it was my connection reference points under my manager's dataverse cloud. I re-created the flow and transferred it to my manager's ownership as he owns the dataverse cloud. I tested it with my team members (of same hierarchy level in the corporation) and the flow has always been successful when tested.

However when the approval was sent to a higher management level say i.e, Executive Manager, they are all having issues approving it. I am not sure if this is something to do with firewall with outlook or what. Can you let me know if this is the same case a you?

Was this reply helpful? Yes No
PPYY 10 on at

Like (0)

Report

By the way, i also created an instant approval flow for a sharepoint list. Although it didnt give the approver an http error but when the approver (an Executive Manager) approves the flow, the flow gets stucked in the 'start and wait for approval' stage and it wont complete the flow. Mind you, this flow was tested many times before it got sent to the EM. The flow worked everytime i sent to my team members for testing and then when it got sent to the EM, it just didnt work. Let me know if you have the same issues too. I am about to put a new post with regards to this issue hopefully someone can share their thoughts

start and wait fo...

Connection Ref Po...

Was this reply helpful? Yes No
MV-04061936-0 6 on at

Like (0)

Report

In my case, the Start and Wait for an approval gets stuck because the approving user cannot click on the Approve or Reject button, they get the error I am mentioning in my post.

The only thing I can actually think about is that users who get this error have some how logged in under another user or email address at some point and the credentials are mixed up.

I will try to get one of my faulty users password and set them up in a brand new desktop environment and see if I have a different result.

Stay tuned.

Thanks!

Was this reply helpful? Yes No
BD-17061953-0 6 on at

Like (0)

Report

I am having the same issue with forms that were working fine in the past. We started seeing this error on May 16th. Power Automate support looked at it and determined the issue is not with power automate (i question this) and passed it on to Outlook support where it has so far gotten nowhere. I am doing the same thing with adding email addresses with variables, however i have some approval steps that are not using a variable and I have seen the issue happen there too.

The problem seems to be hit and miss with us. A user will be able to approve some items in Outlook and some not, with the exact same flow. Doesn't seem to be a rhyme or reason for this happening. We are getting the same 403 error in both Outlook desktop and web.

Was this reply helpful? Yes No