Once we have the ability to accurately measure per-task utilization (#847), we can allow tasks to set utilization limits in terms of reports per time period so that users can protect themselves against unexpectedly large cohorts of clients or unexpectedly frequent report uploads leading to high server costs.
This would also involve some divviup-api plumbing to provide this value during task creation or allow changing it. We may expand this issue into a tasklist tracking various bits of implementation.
Once we have the ability to accurately measure per-task utilization (#847), we can allow tasks to set utilization limits in terms of reports per time period so that users can protect themselves against unexpectedly large cohorts of clients or unexpectedly frequent report uploads leading to high server costs.