Using Workflow to post notification of event in Outlook to Viva Engage

Question

I am just a general user with limited knowledge. I've set up a workflow to celebrate employee birthdays (with their permission) and service anniversaries. This looks at a set calendar in Outlook and checks for upcoming events, when triggered it posts set text to a specified community in Viva Engage.

It was working fine for years but then it kept failing. If I went in to edit it seemed to refresh the connection and then it would work for a few weeks then fail again. It now won't work at all. I have tried editing and then running manually but it fails with error 504.

I found where it showed failed runs and managed to get the code 504. But I have no idea how to fix.

Any ideas? Please keep it to simple instructions :-)

Start time

Dec 22, 11:28 PM (

3 weeks ago3 wk ago

)

Duration

00:00:30

Error

Action 'When_an_upcoming_event_is_starting_soon_(V3)' failed

Bad gateway

 

 

Gateway Timeout

Outputs

Body

{

  "error": {

    "code": 504,

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

    "clientRequestId": "95ca4602-e1a6-47c7-a4e3-69e8a9a3a052",

    "message": "BadGateway",

    "innerError": {

      "status": 504,

      "message": "Request failed. Try again later.\r\nclientRequestId: 95ca4602-e1a6-47c7-a4e3-69e8a9a3a052\r\nserviceRequestId: 5daf1d73-bfdd-4ab7-a5dc-32622af18bc1",

      "error": {

        "message": "Request failed. Try again later."

      },

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

    }

  }

}

Headers

{

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

  "Pragma": "no-cache",

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

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

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

  "x-ms-request-id": "5daf1d73-bfdd-4ab7-a5dc-32622af18bc1",

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

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

  "x-ms-environment-id": "default-813da6e3-969e-4790-b65b-e1964c741099",

  "x-ms-tenant-id": "813da6e3-969e-4790-b65b-e1964c741099",

  "x-ms-dlp-re": "-|-",

  "x-ms-dlp-gu": "-|-",

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

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

  "x-ms-apihub-obo": "false",

  "Date": "Sun, 22 Dec 2024 23:29:29 GMT",

  "Content-Length": "572",

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

  "Expires": "-1"

}

 

Status Code

504

Answer 1

Hi @Caroline Senior,

The HTTP 504 Gateway Timeout server error response status code indicates that the server, while acting as a gateway or proxy. Per my research, this should caused by a recent change to the code base responsible for publishing scheduled publications introduced an error that's preventing the service from detecting when the configured time arrives, leading to impact.

The Microsoft will aim to provide a resolution ETA for the remaining impacted users by next scheduled update at January 21, 2025, at 1:00 AM UTC. Here is the details of the issue report

Here is the link of the issue

https://admin.microsoft.com/adminportal/home?#/servicehealth/:/alerts/MV958947

We will continue to pay attention to this issue, and notify you in time if there is any updates

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.