Forum Discussion
Planner Limitations
SanthoshB1 These numbers are way out of date. Please ignore.
Joanna Parkhurst Seems you have time to correct your support teams, but since Planner is released your product team has no time to publish an official support post about Planner limits? Not understandable. Recently I had also a case for Planner and was so disappointed about the support.
Maybe this support guy understands why customers want to know limits and got from other teams outdated information. How long should customers wait for official limits?
Hi Tobias - we monitor usage and expand accordingly. Limits are present to protect the service. Right now as I write this a deployment is happening to further increase those limits. I can't say what those limits are as the numbers will soon be wrong again - depending when this is read (like the rest of the thread). As a support person it would be nice to point to an exact article, but I also understand why the team are choosing not to do that. If you have a use case that you feel is hampered by your perceived current limits then please share.
Best regards,
Brian
Hi Brian-Smith,
We are aware of limits that are expanding and continuously changing.
That's why you need to continuously publish updates about the current limits as you go along.
A project, critical for the organisation, can't have a risk of failing due to an unknown tool limitation!
It makes me wonder how serious MS is about Planner.
- Seems to be a very awkward situation for Microsoft. The app has extremely high potential, but as it goes with apps like that, seems it has a limitation no one was officially aware of. Now that people raised it, we still don't have an answer. Is there a limit then? Is there not? Is it tenant dependant, license (E3/E5), do we need to pay extra when we hit the limit? What is the limit?
A message to you guys in the dev team, for some of your users knowing the use case is extremely important. You would not want someone use Planner for developing of a critical project, let's say in a Hospital, infrastructure rebuild - and then hit a roadblock of tasks limit. Nobody plans for the planner app to fail.
A lot of users do not use it only for 'Update X or Y' plans, but aim to build their work tracker through Planner. Without knowing when do we hit the limit, the stability of the app is put into question. With stability being unknown, people can't honestly recommend the use of Planner.
Planner is a really good addition to 365. Please rebuild the trust in it, then improve your presence on the Microsoft Roadmap. You are probably not the main revenue driver like SharePoint, Azure or Exchange, but you still should build a solid presence in the 365 Catalog and improve the application's potential.I agree with the frustrations here regarding not having the limits published.
What I've done is used Flow to create tasks in Planner to a scale per the requirements we expect to need to meet. This has allowed us to test if we can use Planner for our scenarios. I think in one scenario I stopped after about 800 tasks in a single bucket.
I didn't hit any limits in the testing but this is purely anecdotal.
Sorry if it will sound kind of harsh, but - Brian-Smith - reading the whole thread long, it just seems to me, that it is a clear intention of MS to actually not provide such info publicly. Please don't hide it behind some collective team decisions - there's always one person responsible for the actual decision and this thread should provide enough of signal to any product manager about how the product is perceived. Ppl are simply feeling insecure. Ppl want to know the numbers for a reason - to plan ahead.
Why is not Planner team inspired by the MS Flow for e.g.? We know actual numbers, we can buy more advanced plans for particular users. Translating to Planner, if we have two assistants to putting-in all the company management tasks, we could buy the higher Plan limit for them. With Flow, you can even buy additional Flows for the whole tenant generally.Of course the question is, what is the Planner's future in general - in the Microsoft 365 Roadmap, I can't see any new features planned for 2019, most of the being just Q1-Q3/2018 ;-)
How can we plan a deployment and not know whether or not we'll have an issue with task limits? Just hope for the best and then give Microsoft a ring when/if we hit them?
I think most people on here are smart enough to realize that limits posted a year ago may not be accurate. It would be helpful for many of us to just know the current limit with the understanding that things change.
Brian, i kind of understand your point, but you say that customers should expect Microsoft to expand limits in a timely manner when their usage reaches them. This is not encouraging. Also Planner is odd among other services that always had and have documented limits and they increase with the time (SharePoint file size, Exhange mailbox, etc.). This is just against regular MS practice.
Brian,
We regularly have use cases where a single person will need to create many hundreds of work items and maintain them for the duration of the project as part of the project record; deleting old items is a non-starter from a metrics perspective.
Please keep this in mind: the more important / larger / complex the project, the closer we get to, or hit, these limits. Without disclosure it is unlikely that we can recommend this product on a project of any significant impact. Too risky.
I hope this helps.
