Microsoft-graph-docs: Upload to OneDrive returning 504 Gateway Timeout (Unknown error )

[kritika28saxena]

Problem:

I am trying to upload images to one drive and frequently getting error:

504 Gateway Timeout (Unknown error ).

API used:

PUT   https://graph.microsoft.com/v1.0/users/{userId}/drive/items/{rootFolderId}/{folderPath}/{fileName}:/content

Response (504 Gateway Timeout):

{
  "error": {
    "code": "UnknownError",
    "message": "",
    "innerError": {
      "request-id": "9709847a-36d4-42f2-90dd-4c37094caead",
      "date": "2018-05-16T12:18:37"
    }
  }
}

Also asked on Stack Overflow

Do you have any idea what is causing this? Or could it be fixed please.

[prystoynyy]

Hi!

Sometimes I get 504 Gateway Timeout error while trying to create a folder, too

POST
https://graph.microsoft.com:443/v1.0/groups/{groupId}/drive/root:/{folderPath}:/children

[agallart]

hi
you can try create folder and then put the file , I'm doing this and I haven't any error

first
Dim item = New DriveItem() item.Name = folder item.Folder = New Folder() Dim createFolder = graphClient.Me.Drive.Root.Children.Request().AddAsync(item)

and then

Dim file = graphClient.Me.Drive.Root.ItemWithPath(folder + "/" + filename).Content.Request().PutAsync(Of DriveItem)(fileContentStream)

[boomych]

The same problem
PUT /v1.0/groups/{group_id}/drive/root:/{path_and_filename}.xlsx:/content

Result code 504

[CaramelHeaven]

Hello @kritika28saxena. Have you found any solution how to solve this problem?

[Kritika2808]

hey @CaramelHeaven , I tried to connect with Microsoft team also but didn't get any luck there.
So for handling above condition, I have incorporated retrial mechanism.

If I get these errors, I retry the API at regular intervals three times.

It has solved my issue for now.

[prystoynyy]

Hi @jthake-msft

The issue is still reproducing.

I have created a repository prystoynyy/msgraph-onedrive-issue which will help you to reproduce the bug more easily

[jthake-msft]

I'm sorry to have to do this to you. We have a new triage process that our customer experience team are monitoring on our official channel for questions. This is StackOverflow with 'microsoft-graph' tag. Old stack posts will be picked up.

I was trying not to close these off here in the documentation GitHub issues repo and get them answered. This issues lists is specifically for documentation issues, not the underlying service, sdks or samples.

It's proving too hard for me to be single point of failure here in assigning the correct engineers to answer questions. It is best for questions to go on StackOverflow where they'll be monitored by a dedicated team and escalated internally to PMs through a defined process.

[jthake-msft]

As an alternate to StackOverflow for raising issues. You can also raise a support ticket that will be look at by the support engineers. This simple video shows how to file it properly starting here.