Upper limits for running and managing tasks

Document advisory for running and managing lots of tasks.

From a recent [Slack thread](https://influxdata.slack.com/archives/C89G3JD2R/p1659467670567709):

Are there any guidelines on an upper limit of tasks that you can run in Cloud?

6 replies

- For cloud at least, we have customers with 10,000's of tasks, the problem is usually they run into timeout limits for task execution, so somewhat short tasks you can run a ton of

- There is also a query duration limit - number of minutes of execution time that a single customer can use in a window. (I make a distinction between this limit and “timeouts”)

- You will also have a hard time using the UI to manage them effectively if you have many thousands (customers with those numbers use some automation against the API to create and update them, generally)

- Re the aggregate time limits Phil mentioned, using the offset setting can be helpful to spread tasks out a bit if a customer hits those limits

Start with the linked Slack thread, then identify where task limits and task-management guidance belong in the documentation. Done means an advisory covering task volume, execution timeouts, aggregate query-duration limits, UI and API management at scale, and using offsets to spread execution.

Written by the indexing model from the issue text.