Forum Discussion
Planner Limitations
SanthoshB1 These numbers are way out of date. Please ignore.
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.
