Bad Request error when extracting ZIP archive to Onedrive folder

[2DM]

I am getting a 'Bad Request' error when I try to unarchive a '.zip' file on Onedrive. 

I tried different things some things like changing the destination path but for some reason, I can't get it to work.

Any suggestions on how to fix this?

[pre]

Hi @2DM ,

May I confirm if you have created flow with the below steps included in it::

When a file is created in a folder
Create File 
Extract Archive to folder 

Try the above and check if that works .If still the same issue , please share some inputs on the flow with any snapshots so that can try to reproduce it at my end and let you know the detail .

Thanks

[2DM]

Hi @pre 

I've configured mine a bit differently, please see below. 

The file comes from an HTTP GET request and I've input the body from this request as file contents to create a ZIP file. The original file from the API is a .gz but I think changing it to .zip shouldn't cause any problems. The file actually gets created (I checked) in my Onedrive and when I download it on my PC I can unarchive it without any problems. Within the zip file is a text file I need to get to. 

Here's my setup:

And here are the raw inputs:

{
    "host": {
        "connectionReferenceName": "shared_onedriveforbusiness",
        "operationId": "ExtractFolderV2"
    },
    "parameters": {
        "source": "/Test Flow/streams23_07_2021.zip",
        "destination": "/",
        "overwrite": true
    }
}

These are the raw outputs I get:

{
    "statusCode": 400,
    "headers": {
        "Pragma": "no-cache",
        "Transfer-Encoding": "chunked",
        "x-ms-request-id": "b274d167-eeb6-440e-994d-dd5298cf8bb7",
        "Timing-Allow-Origin": "*",
        "x-ms-apihub-cached-response": "true",
        "Cache-Control": "no-cache",
        "Date": "Fri, 23 Jul 2021 11:21:36 GMT",
        "X-AspNet-Version": "4.0.30319",
        "X-Powered-By": "ASP.NET",
        "Content-Type": "application/json",
        "Expires": "-1",
        "Content-Length": "147"
    },
    "body": {
        "status": 400,
        "message": "Unable to extract contents of file '/Test Flow/streams23_07_2021.zip'.",
        "source": "api.connectorp.svc.ms"
    }
}

[2DM]

Hi @pre 

I my setup is a little bit different. I get my ZIP file from an HTTP request where I create a file with the body as contents.  When I manually download the created file and unarchive it on my PC, I can do it without any problems.

Please see my setup below:

Here are the raw inputs:

{
    "statusCode": 400,
    "headers": {
        "Pragma": "no-cache",
        "Transfer-Encoding": "chunked",
        "x-ms-request-id": "74607b77-33d2-4bf0-8f16-8c4933e471fc",
        "Timing-Allow-Origin": "*",
        "x-ms-apihub-cached-response": "true",
        "Cache-Control": "no-cache",
        "Date": "Fri, 23 Jul 2021 11:37:17 GMT",
        "X-AspNet-Version": "4.0.30319",
        "X-Powered-By": "ASP.NET",
        "Content-Type": "application/json",
        "Expires": "-1",
        "Content-Length": "147"
    },
    "body": {
        "status": 400,
        "message": "Unable to extract contents of file '/Test Flow/streams23_07_2021.zip'.",
        "source": "api.connectorp.svc.ms"
    }
}

Here are the raw outputs:

{
    "statusCode": 400,
    "headers": {
        "Pragma": "no-cache",
        "Transfer-Encoding": "chunked",
        "x-ms-request-id": "74607b77-33d2-4bf0-8f16-8c4933e471fc",
        "Timing-Allow-Origin": "*",
        "x-ms-apihub-cached-response": "true",
        "Cache-Control": "no-cache",
        "Date": "Fri, 23 Jul 2021 11:37:17 GMT",
        "X-AspNet-Version": "4.0.30319",
        "X-Powered-By": "ASP.NET",
        "Content-Type": "application/json",
        "Expires": "-1",
        "Content-Length": "147"
    },
    "body": {
        "status": 400,
        "message": "Unable to extract contents of file '/Test Flow/streams23_07_2021.zip'.",
        "source": "api.connectorp.svc.ms"
    }
}

[pre]

Hi @2DM ,

Thank you for sharing the detail . The status code 400 indicates an invalid request been sent . Please check with a different URI definition . You can also check by entering the URI information instead of selecting the dynamic content . 

To isolate the issue more , can you please share the failed flow URL from the edit screen of the flow in run history .

Thanks

[2DM]

I've checked and the problem isn't with the URI information. 

Here's the failed flow URL:

https://emea.flow.microsoft.com/manage/environments/Default-7e131bef-6163-417e-8913-eb8a434e87af/flo...

[pre]

Hi @2DM ,

Thank you for sharing the flow URL. I see that the there is a failure happening for the API ID -  onedriveforbusiness . And backend URL is "https://api.connectorp.svc.ms/datasets/default/extractFolderV2?source=_&destination=_&overwrite=_" 

You might need to check with your admin if there is any restriction policy applied in regards to onedrivefor business API call .

Thanks

[Anonymous]

I have the same issue.

Anyone have a update about this situation? 

[gcpreston]

I am also facing this issue. Did you manage to resolve it?