Managing your quotas
Every account has a daily execution quota for scheduled tasks. The quota stops you (and the rest of the tenant) from accidentally racking up an LLM bill with a misconfigured task.
This page covers how to read your quota, what changes when you hit it, and what to ask an admin if your default isn't enough.
Defaults
Three quota templates ship with QRY:
| Template | Daily executions |
|---|---|
| Standard | 100 |
| Monitoring | 300 |
| Power user | 500 |
Your account inherits a template through this resolution order:
- Per-user override — an admin set a specific number on your account.
- Group default — your group (e.g. data-team) has a non-default template.
- System default — Standard, unless your tenant's admin overrode it.
- Hardcoded fallback — 100/day, used only if all the above are unset.
Where to see your quota
Open Scheduled Tasks (≡ → Scheduled Tasks). Each row's Executions column shows your current usage:
33 / 42
The first number is successful runs in the rolling 24-hour window for that task; the second is total attempts (including failures, which still count against quota). Across all your tasks, the daily total is what your quota caps.
The Cost column shows the rolling-30-day spend in your tenant's billing currency, which is independent of the quota — you can hit cost limits without hitting the quota or vice versa.
What happens when you hit the quota
The next scheduled execution after you hit the limit silently fails with a quota exceeded error and the task remains active. It will retry on its next scheduled tick (which by then is in the next quota window if enough time has passed).
Tasks themselves are not auto-disabled by quota — only by 3 consecutive failures of any other kind.
The quota window is rolling, not aligned to UTC midnight. You don't get a daily "reset moment"; instead, executions older than 24 hours stop counting against you.
What to do when you hit it regularly
In rough order of effort:
1. Trim what's running
Open Scheduled Tasks, sort by Executions, and look at the most-frequent ones. Common patterns that burn quota:
- An hourly task that could be daily.
- A weekly summary that you set up but no longer read.
- A noisy monitoring task with redundant checks.
Pause or delete the ones you don't need.
2. Consolidate
Two tasks that both query the same table can often be combined into one notebook with multiple cells, scheduled once.
3. Ask for a quota bump
If you legitimately need more (e.g. you're operating real monitoring), ask an admin to either:
- Move you to the Monitoring (300/day) or Power user (500/day) template.
- Set a per-user override.
See Task Quota Templates for the admin side.
Common issues
A task shows Executions 0 / 0 hours after creation. The first scheduled tick hasn't fired yet, or your timezone setting moved it later than you thought. Check the task's Next Run time.
Successful executions but a quota exceeded in the audit log.
Some attempts within the same hour exceeded the per-minute or per-task burst limits, separate from the daily quota. Spread the schedule out (e.g. don't run 30 tasks all at 09:00:00).
Cost is high but quota usage is low. A few expensive runs (heavy notebooks, long context, expensive models) cost more than many cheap ones. Cost and quota are independent; admins can see per-task cost in the management view to track which task is expensive.
Auto-disable triggered before I hit my quota. Auto-disable comes from 3 consecutive failures, not from quota — it's the same trigger regardless of why the runs failed. Check the task's last 3 executions.
See also
- Creating a scheduled task — the canonical creation walkthrough.
- Output channels — conversation vs. email.
- Task Quota Templates reference — admin configuration.