Bad Gateway 502 after Export/Import

[Anonymous]

Hello guys.

I have, as i can see common problem, which is code 502 "BadGateway". I imported-exported a flow I've made to my colleague, but after an import that flow onto His account, this error appears. This error occurs at the verry beggining of the flow (1st trigger) "when a new message arrives". 

I'm a begginer in the IT so please try to be, as much as possible detailed

 "error": {

    "code": 502,

    "source": "flow-apim-europe-001-westeurope-01.azure-apim.net",

    "clientRequestId": "146f91e0-70f2-4ea9-912b-6f5b217f84c0",

    "message": "BadGateway",

    "innerError": {

      "status": 502,

      "message": "Operation: Create; Exception: [Status Code: ServiceUnavailable; Reason: Mailbox move in progress. Try again later., Cross Server access is not allowed for mailbox 11975779-ec89-43c7-8969-dd65468d4995]\r\nclientRequestId: 146f91e0-70f2-4ea9-912b-6f5b217f84c0\r\nserviceRequestId: f541344f-0682-4e8f-a383-038f9c0a0e27",

      "error": {

        "message": "Operation: Create; Exception: [Status Code: ServiceUnavailable; Reason: Mailbox move in progress. Try again later., Cross Server access is not allowed for mailbox 11975779-ec89-43c7-8969-dd65468d4995]"

      },

      "source": "office365-ne.azconn-ne-01.p.azurewebsites.net"

    }

  }

}

Thank You form advanced guys! 

[ScottShearer]

@Anonymous 

Can you tell me if this issue was resolved after waiting a while and trying the Flow again?

[Anonymous]

Unfortunatelly not. After the weekend it's still appears. Maybe informations form 2nd frame will be helpfull:

"Pragma": "no-cache",

  "x-ms-datasourceerror": "True",

  "x-ms-request-id": "9ec58059-f144-44f6-b7e5-811c936bf187",

  "Strict-Transport-Security": "max-age=31536000; includeSubDomains",

  "X-Content-Type-Options": "nosniff",

  "X-Frame-Options": "DENY",

  "Cache-Control": "no-store, no-cache",

  "Set-Cookie": "ARRAffinity=b4a5d5fe349f4c875ad3d8ac25e07615025468d24d2831b4f4987af0338dc44a;Path=/;HttpOnly;Secure;Domain=office365-ne.azconn-ne-01.p.azurewebsites.net,ARRAffinitySameSite=b4a5d5fe349f4c875ad3d8ac25e07615025468d24d2831b4f4987af0338dc44a;Path=/;HttpOnly;SameSite=None;Secure;Domain=office365-ne.azconn-ne-01.p.azurewebsites.net",

  "Timing-Allow-Origin": "*",

  "x-ms-apihub-cached-response": "false",

  "Date": "Mon, 22 Nov 2021 15:33:38 GMT",

  "Content-Length": "906",

  "Content-Type": "application/json",

  "Expires": "-1"

Thank you for help .

[ScottShearer]

@Anonymous 

In your original post you say the following:

"I imported-exported a flow I've made to my colleague, but after an import that flow onto His account, this error appears."

Can you explain what you mean when you say "an import that Flow into his account".  Did you have the user import the Flow and provide his own credentials upon import?

[Anonymous]

I followed with this instruction : https://www.thirdtier.net/2021/05/26/how-do-i-export-and-import-a-flow-from-power-automate/

While I was importing, I Did connect His account to the flow rules and necessary Triggers (Outlook, OneDrive and SharePoint)

[Anonymous]

Ok I fixed the bug. After Import I should have done the flow test. After It, green ticks appeared.

Thank You for Your Interest.