Planner API keeps timing out

%3CLINGO-SUB%20id%3D%22lingo-sub-1572937%22%20slang%3D%22en-US%22%3EPlanner%20API%20keeps%20timing%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1572937%22%20slang%3D%22en-US%22%3E%3CP%3EStarting%20around%207%2F31%2C%20our%20Planner%20API%20started%20timing%20out%20to%20the%20point%20that%20we%20cannot%20finish%20a%20run.%20We%20had%20successfully%20manually%20run%20the%20request%20around%209%20am%2C%20but%20that%20did%20not%20even%20work%20yesterday.%20We%20were%20running%20the%20API%20at%205AM%2C%20so%20we%20changed%20it%20to%203AM.%20We%20have%20also%20increased%20the%20number%20of%20attempts.%20Our%20plan%20is%20very%2C%20very%20big.%20Since%20March%202019%2C%20we've%20been%20using%20it%20as%20a%20critical%20part%20of%20our%20request%20management%20system%2C%20connected%20by%20flow%20to%20other%20Microsoft%20products%2C%20with%20around%20150%20users%20and%20over%205000%20requests).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20issue%20appears%20to%20be%20from%20an%20unhandled%20exception%20and%20some%20of%20the%20requests%20were%20timing%20out%20because%20of%20the%20large%20number%20of%20requests.%20We%20use%20the%20API%20for%20critical%20reporting%20and%20visibility.%20We've%20noticed%20the%20time%20it%20occurs%20at%20is%20exactly%201%20hour.%20Is%20it%20possible%20it%20is%20related%20to%20the%20token%20expiring%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20Suggestions%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1733028%22%20slang%3D%22en-US%22%3ERe%3A%20Planner%20API%20keeps%20timing%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1733028%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F222445%22%20target%3D%22_blank%22%3E%40Shiann%20Weiss%3C%2FA%3E%26nbsp%3B-%20Since%20no%20one%20answered%20this%2C%20I%20will%20answer%20it.%20We%20used%20the%20Planner%20API%20and%20pulled%20all%20the%20detail%20that%20we%20could%2C%20I%20save%20that%20info%20in%20a%20spreadsheet%20for%20my%20reporting%20and%20we%20then%20used%20the%20API%20to%20remove%2075%25%20of%20the%20old%20records.%20Before%20then%2C%20the%20API%20was%20timing%20out%20and%20we%20made%20a%20few%20adjustments%20but%20it%20was%20wishy%20washy.%20In%20short%2C%20Planner%20API%20can't%20handle%20it%2C%20you%20have%20to%20reduce%20your%20tasks.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Starting around 7/31, our Planner API started timing out to the point that we cannot finish a run. We had successfully manually run the request around 9 am, but that did not even work yesterday. We were running the API at 5AM, so we changed it to 3AM. We have also increased the number of attempts. Our plan is very, very big. Since March 2019, we've been using it as a critical part of our request management system, connected by flow to other Microsoft products, with around 150 users and over 5000 requests).

 

The issue appears to be from an unhandled exception and some of the requests were timing out because of the large number of requests. We use the API for critical reporting and visibility. We've noticed the time it occurs at is exactly 1 hour. Is it possible it is related to the token expiring?

 

Any Suggestions?

1 Reply
Highlighted

@Shiann Weiss - Since no one answered this, I will answer it. We used the Planner API and pulled all the detail that we could, I save that info in a spreadsheet for my reporting and we then used the API to remove 75% of the old records. Before then, the API was timing out and we made a few adjustments but it was wishy washy. In short, Planner API can't handle it, you have to reduce your tasks.