Schedules and limits

How often Scout runs each job

Job	Frequency
Pre-match detection	every 30 seconds
Post-match polling	every minute
Scheduled report dispatch	every minute
Competition lifecycle	every 15 minutes
Report data fold	every 15 minutes
Channel and guild validation	hourly
Match-time refresh	every 6 hours
Full report data rebuild	daily, 02:00 UTC
Orphaned player pruning	daily, 03:00 UTC
Removed-guild cleanup	daily, 04:00 UTC

Practical consequences:

A pre-match card lands within about 30 seconds of a game starting.
A recap lands within about a minute of a game ending.
A game finished moments ago may not appear in a report for up to 15 minutes. Notifications do not wait for this.

Report schedule presets

Preset	Cron
Daily — midnight	`0 0 * * *`
Daily — 9am	`0 9 * * *`
Daily — noon	`0 12 * * *`
Weekly — Sunday midnight	`0 0 * * 0`
Weekly — Monday midnight	`0 0 * * 1`
Monthly — 1st midnight	`0 0 1 * *`

Any valid five-field cron expression can be entered instead. Schedules fire in the timezone set on the report, not UTC and not the reader’s timezone.

Query and report limits

Limit	Value
Query text	4000 characters
Outputs per `SELECT`	1–20
Grouping dimensions	1–2
Lookback window	up to 31 days, 30 by default
Rows returned	up to 25, 10 by default
Chart series	1–8
Report title	100 characters
Report description	500 characters

Per-server limits

Scout caps, per Discord server:

tracked players with subscriptions,
Riot accounts,
saved reports, and reports owned by any one person.

The exact values are configured per server and may be unlimited. Scout warns as you approach a cap — within five remaining slots — and tells you the current count and maximum when you hit one.

Discord command limits

Limit	Value
Subscriptions shown by `/list`	25
Player alias length (`/track`)	1–100 characters