MS Flow approvals don't work: Encountered internal server error from the XRM API.

[DenisMolodtsov]

Does anyoe know why we cannot approve/decline anything?

When we click on "Approve" or "Declined" and then "Submit" - we just get an error: "Encountered internal server error from the XRM API. "

More details

- We are using non-default environment

- Database for the envrionment is created (took ~50 minutes)

- We are using a free MS Flow license to test the flow. We do have Plan 2 licenses, but only to create environments.
- If we go to the https://canada.flow.microsoft.com/manage/environments site and then click on the approval the screen never finish loading. It's just blank.

- Googling "Encountered internal server error from the XRM API." error yelded no results

I can provide any addition information if needed!

Any help or comments will be greatly appreciated. 

[v-yamao-msft]

Hi @DenisMolodtsov,

What’s your current situation? Are you still having the issue?

Does it work for you before?

I am not sure if there are any updates in your region. I have tested it in a non-default environment and the region is Asia, the page of Start an approval works fine.

Could you please try with a different region on your side?

Best regards,

Mabel Mao

[DenisMolodtsov]

The situation is this:

- Q: Did it work earlier? 

- A: We are only starting to develop Approval workflows. We did have multiple Flows already, but non of them contained approval steps.

- Q: Do we still have an issue?

- A: yes, we still do.

Update:

- Q: Did you try other regions?

- A: Yes, we have just tested Environment created in the US region and approvals/rejecitons come through with no errirs. All Canadian-based non-default environments manifest the issue described.

I have tried approvals in 4 different tenants and 4-5 non-default environments that are all in the Canadian region. All default environments work just fine. None of the non-default environments can approve or reject any Approval requests. US-based environment works. 

1. Development tenant (Where we develop everything). Environments:

- Default (Canada). Approvals work

- Dev (Canada). Env. Type: Production. Approvals cannot be accepter/rejected (Encountered internal server error from the XRM API...)

- Test (Canada). Env. Type: Production. Approvals cannot be accepter/rejected (Encountered internal server error from the XRM API. The tracking Id is '1d585244-af90-4ca0-9ac8-c338985ba57c'.)

2. Personal Business essentials tenant. Environments:

- Default (Canada). Approvals work

3. Office365 free Dev tenant. Environments

- Default (Canada). Approvals work

4. Production tenant 1. Environments:

- Default (Canada). Approvals work

- Staging (Canada). Approvals cannot be accepter/rejected . See example below

- Dev (Canada). Approvals cannot be accepter/rejected

- US (US region) Approvals/rejections work with no issues

[DenisMolodtsov]

Update:

We have found two old Canadian envrionments created on June 6th. Approvals/Rejections work there. But these are old throwaway Envrionments we are not using.

[DenisMolodtsov]

Way to replicate the issue:

- Create a new environment in Canadian region. (yes, new. and yes, pick Canadian region. Don't test it against 6 months old envrionments)

- Create a simple approval Flow

- Run it and see what happens. Did you get an email? Can you approve/declone?

[evel]

There are some issues in approvals: https://flow.microsoft.com/en-us/support/. 

[DenisMolodtsov]

It's nice to know that we are not alone with this issue. I am really curious though what is going happen. Is there any more information apart from this short message?

Warning: Starting September 10, 2018 at 4:00pm PDT, users may recieve errors when attempting to respond to approvals in some environments.

[dkappes · Accepted solution]

Hello, we have deployed a fix. Will you please give it another try?

[DenisMolodtsov]

@dkappes Thank you! I have just tested approvals and they are finally  getting through. I can approve and reject. I will keep an eye on it, but so far it seems to be working fine.

[dkappes]

Thank you so much for your patience, and I apologize for the inconvenience. An underlying API unexpectedly changed behavior in some (mostly newer) environments and it took us a while to root cause it.

[Anonymous]

@dkappes 

Running into this error as of first thing this morning with Approvals in MS Flow.  Getting the error message: 

"Encountered internal server error from the XRM API" then it provides the GUID.  

We're building business processes on this... can someone please do regression testing before releasing changes??

[Anonymous]

I second that comment - please do regression testing!

We have a business-critical process that relies on Flow (Power Automate) and approvals, with option to reassign approval. Today, we are unable to reassign - get the lovely internal server error.

[AAArrington]

Same here, this error is holding up several processes of ours. 

[dkappes]

Hi. Yes, we did recently introduce a regression in the reassignment behavior. The fix is currently deploying and is currently scheduled to reach the US on Monday, 12/9.