# What runs when > Everything Scout does on its own and on what schedule, the one cadence you control, and the actions that never happen without a person pressing a button. Audience works while you are not looking at it. Most of what Scout does happens on a schedule: syncing your search data overnight, re-scoring the queue, asking the AI visibility panel each morning, proposing rules once a week. This page lists all of it, so nothing that appears on Home or in Activity is a surprise. ## On a schedule | When | What Scout does | Why it matters | | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Every night | Syncs the latest Search Console data, then Analytics if it is connected. | Search figures always run two to three days behind, whatever tool reads them. | | Every night | Re-scores every open opportunity against the fresh search data. | A flagged topic whose demand climbed above the minimum clears its guardrail and returns to the queue on its own. Scores on open topics refresh daily whatever your rebuild cadence. | | On your cadence | Rebuilds the opportunity queue: reads the market again, regroups keywords into articles, and judges each group against your company profile. | The expensive path, and the one that finds new topics. See below. | | Weekly | Refreshes keyword demand and live rankings for topics that are open or in progress. | Scoped to active work, so a workspace with nothing shortlisted costs nothing here. | | Daily | Takes a performance snapshot of every page Scout published. | Feeds Content performance and the single-page reports. | | Every morning | Asks the confirmed AI visibility panel, for workspaces that have one. | The recurring spend the panel screen warns about. See [Costs and cadence](/ai-visibility/costs-and-cadence). | | Weekly | Reads the pages assistants cited, to see whether they list you. | Turns "cited a roundup" into "a roundup to earn a place on" or "a placement to improve". | | Weekly | Proposes learned playbook rules from the last two months of your edits. | Why the Learned tab fills weekly, not daily. See [Learned rules](/playbook/learned-rules). | | Weekly | Looks for patterns across your published work and writes them up as insights. | "What Scout has noticed" on Reports. | | Weekly and monthly | Writes the report narrative for the week and the month just finished. | The summary card at the top of the Reports overview. | | Every few minutes | Checks for runs that stopped without finishing and closes them. | Why a failed run never sits as "running" forever. See [Activity](/automation/activity). | ## The one cadence you control The rebuild is the only scheduled job with a setting, because it is the one that costs. In Workspace settings, **Rebuild opportunities** offers: **Every day**, **Every three days**, **Every week**, **Every two weeks**, or **Only when I ask**. The help text beside it is the whole trade-off: > A full rebuild reads the market again, so more often costs more. Scores on open opportunities refresh daily either way, and you can always research a topic on demand. Weekly is the default and suits most teams. Choose **Only when I ask** if you would rather trigger rebuilds yourself and rely on [Research a topic](/opportunities/research-a-topic) between them. See [Workspace and members](/settings/workspace-and-members) for where the setting lives. ## Nothing that spends money happens on arrival Opening a page never costs anything. Every action that spends is a button a person presses: - **Research a topic** and its variants on the AI visibility screens. - **Suggest questions**, **Run now** and **Measure it now** on AI visibility. - **Re-read my site** on the Playbook. - **Move forward** on an opportunity, which starts research and drafting. - **Approve outline & start drafting** and **Write it again** on the outline. - **Retry** on a failed run. And nothing happens optimistically. When you approve, reject, accept or dismiss, the screen waits for the server to confirm before it shows the change. ## While Scout works Screens that have something in flight poll themselves and stop when it settles: Home and Opportunities every few seconds while a scan runs, an article's record while Scout is drafting, the setup screen throughout the build. You can leave any of them. The sidebar indicator shows **Scout is working** wherever you are, and [Activity](/automation/activity) shows every run and every agent call as it happens.