Here is the full Headers and Body output from the flow:
Headers
| Pragma | no-cache |
| Transfer-Encoding | chunked |
| x-ms-datasourceerror | True |
| x-ms-request-id | 75d0ac25-c2a0-4fb1-8cc3-320e... |
| Timing-Allow-Origin | * |
| x-ms-apihub-cached-response | true |
| Connection | close |
| Cache-Control | no-cache |
| Date | Mon, 09 Mar 2020 16:09:36 G... |
| X-AspNet-Version | 4.0.30319 |
| X-Powered-By | ASP.NET |
| Content-Type | application/json |
| Expires | -1 |
| Content-Length | 362 |
Body
{
"error": {
"code": 504,
"source": "unitedstates-002.azure-apim.net",
"clientRequestId": "75d0ac25-c2a0-4fb1-8cc3-320ebcc2c4d3",
"message": "BadGateway",
"innerError": {
"status": 504,
"message": "Request timed out.\r\n inner exception: A task was canceled.",
"source": "api.connectorp.svc.ms"
}
}
}
Please remember, this is ONLY happening for some users. It works fine for others.
Regarding your suggestion to try entering a the Folder Path and Search Query manually and switching to OneDriveSearch, this does not seem to error out for one of the users, but it also does not find the file in the search query for that user nor for myself. I suspect there is a bug in using OneDriveSearch:
Screenshot of the modified search step
Screenshot of the contents of the searched folder
As you can see from the screenshots, the file I am searching for exists, but does not come up using your suggested method.