Something went wrong while loading the results.

Question

Hi Team,

Seems like we cannot search history in MS teams due to an internal error: throttling specifically.

I could reproduce this in both desktop and web versions. As paying users, it is vital for us to search chat history. We would be glad if you can take action to fix this sooner.

The network response looks as follows;

{"error":{"code":"InternalServerError","message":"An exception occurred","target":"","details":[{"code":"InternalServerError","target":"","details":[{"code":"InternalServerError","target":"","details":[{"code":"InternalServerError","target":"","details":[{"code":"FanoutExternalThrottle","message":"Multi-dimension request execution failed after 5 Total user/arbitration/group/archive columns failed. Failure threshold is 4. 0 User, 5 Group failures. Primary Failure Reason: Column Failed with Primary Reason: LSS Failed with Status Code TooManyRequests, ErrorCodes: 429:5;","target":"","details":[{"code":"TwoStepFanout_FirstStepFailed","message":"The call failed, please try again.","target":"","serviceName":"Xap","moduleName":"SubstrateSearch.FanoutV2.Plugins.TeamsSearchMultiDimensionFanoutPlugin","contactTeam":"3sdri","httpCode":500},{"code":"FanoutExternalThrottle","message":"Multi-dimension request execution failed after 5 Total user/arbitration/group/archive columns failed. Failure threshold is 4. 0 User, 5 Group failures. Primary Failure Reason: Column Failed with Primary Reason: LSS Failed with Status Code TooManyRequests, ErrorCodes: 429:5;","target":"","serviceName":"FanoutService","moduleName":"Fanout","contactTeam":"3sdri","httpCode":429}],"serviceName":"FanoutService","moduleName":"Fanout","contactTeam":"3sdri","httpCode":429}],"moduleName":"SubstrateMultiDimensionFanoutSearchWorkflowBase","httpCode":429}],"moduleName":"TenantSearchTeamsFanoutWorkflow","httpCode":429}],"moduleName":"FederationWorkflow","httpCode":429}],"moduleName":"TopLevelWorkflowBase","httpCode":429},"Instrumentation":{"TraceId":"cac13ed2-8690-4864-2ceb-33db331021ce"}}

Regards,
Tharaka

Answer 1

TwoStepFanout_FirstStepFailed is an error we are encountering also:

We're having a live issue nightmare with our Sharepoint queries via lists that have previously worked absolutely fine up until recently on an SPO repository containing ~5m records. In the absence of timely support, we are now investigating using Search through the Graph API. We can get it to pull records back up (including our custom fields) up until the point that we add a "SortBy" to the query (the sort is essential for our users). We are sorting on an indexed custom date field. At the point that we do this we get an internal server error that has similarities to the above. Sandwiched into various error codes that are not recogniseable to us there is a "TwoStepFanout_FirstStepFailed" included. The entire error is below. Please note that we have a premium support ticket open with MS for this for over a week:

Query:

{
"requests": [
{
"entityTypes": [
"listItem"
],
"query": {
"queryString": "SCClaimIDOWSNMBR:219886 path:\"https://companyname.sharepoint.com/sites/TheSiteName/Shared%20Documents\""
},
"sortProperties": [
{
"name": "SCFileReceivedDateOWSDATE",
"isDescending": "true"
}
],
"from": 0,
"size": 100,
"fields": [
"SCFileReceivedDateOWSDATE",
"SCIncidentNumberOWSTNMBR"
]
}
]
}

Result:
{
"error": {
"code": "InternalServerError",
"message": " The call failed, please try again. The call failed, please try again. The call failed, please try again. The call failed, please try again. The call failed, please try again. The call failed, please try again. The call failed, please try again. The call failed, please try again.",
"target": "",
"details": [
{
"code": "InternalServerError",
"message": "The call failed, please try again.",
"target": "",
"details": [
{
"code": "InternalServerError",
"message": "The call failed, please try again.",
"target": "",
"details": [
{
"code": "InternalServerError",
"message": "The call failed, please try again.",
"target": "",
"details": [
{
"code": "InternalServerError",
"message": "The call failed, please try again.",
"target": "",
"details": [
{
"code": "FanoutDownstreamContradiction",
"message": "The call failed, please try again.",
"target": "",
"details": [
{
"code": "TwoStepFanout_FirstStepFailed",
"message": "The call failed, please try again.",
"target": "",
"level": "Error",
"serviceName": "Xap",
"moduleName": "SubstrateSearch.FanoutV2.Plugins.TenantSearch.TenantSearchMultiDimensionFanoutPlugin",
"contactTeam": "3sdri",
"httpCode": 500
},
{
"code": "FanoutDownstreamContradiction",
"message": "The call failed, please try again.",
"target": "",
"level": "Error",
"serviceName": "FanoutService",
"moduleName": "Fanout",
"contactTeam": "3STenantSearchDevs",
"httpCode": 500
}
],
"level": "Error",
"serviceName": "FanoutService",
"moduleName": "Fanout",
"contactTeam": "3STenantSearchDevs",
"httpCode": 500
}
],
"level": "Error",
"moduleName": "SubstrateMultiDimensionFanoutSearchWorkflowBase",
"httpCode": 500
}
],
"level": "Error",
"moduleName": "G21AscWorkflow",
"httpCode": 500
}
],
"level": "Error",
"moduleName": "TenantFileSearchFederationWorkflow_ASC",
"httpCode": 500
}
],
"level": "Error",
"moduleName": "FederationWorkflow",
"httpCode": 500
}
],
"level": "Error",
"moduleName": "TopLevelWorkflowBase",
"httpCode": 500
},
"instrumentation": {
"traceId": "1abfd958-82d9-3dbc-3729-758f06eee82c"
}
}