🔄 Auto-refresh
A source can re-check itself on a schedule and index anything new, so your agents don't quietly go stale. On the Sources tab, a source doing this shows the Live status, and its Keeps in sync column says how often it checks.
Turning it on
- When you add a website or GitHub repository, choose Keep in sync: Daily or Weekly. Off leaves the source as it is until someone syncs it.
- Later, open the source's row menu on the Sources tab and select Change schedule. The Sync schedule window holds the Auto-refresh switch and Check every.
For a website you also choose What to look for:
| Option | When to use it |
|---|---|
| New content | Most sites: picks up pages that weren't there before. |
| Changes to existing pages | "Best for a few pages that change in place, like pricing or status pages." |
Changing the schedule takes a knowledge manager: the Owner, an Admin, or a member with + Knowledge.
What is on by default
When you add a source, Fren One picks a sensible default based on how that type behaves.
| Source type | Default | Checks every |
|---|---|---|
| X profile | On | 6 hours |
| Telegram admins | On | 6 hours |
| Discord admins | On | 6 hours |
| YouTube channel | On | 24 hours |
| Website | Off, unless you choose Keep in sync | Daily or weekly when enabled |
| GitHub | Off, unless you choose Keep in sync | Daily or weekly when enabled |
| Uploaded files, single video | Off | Not applicable, the content does not change |
Websites are off by default because most sites change rarely and a schedule you did not ask for should not spend your credits. Turn it on for a docs site or changelog that genuinely moves.
GitHub is off by default for a different reason: a refresh currently re-reads the whole repository rather than only what changed since the last commit, which makes a frequent schedule more expensive than it is worth. Use Sync now after a docs release instead.
What a refresh actually does
Looking for New content adds, it does not replace. A website refresh looks for pages that are not already indexed and indexes those; an X refresh fetches the most recent posts and keeps the ones you do not already have. Nothing you have is thrown away, and nothing already indexed is charged again.
If a check finds nothing new, it costs nothing.
The schedule adapts
A source that keeps returning nothing new is checked progressively less often: the interval doubles each time, up to a ceiling of about two weeks. A website checking Changes to existing pages slows down less: at most to four times its normal interval. The moment a check does find something, the interval resets to its normal cadence.
So a changelog that updates weekly settles at roughly a weekly rhythm on its own, and an archive that never changes stops being polled almost entirely. You do not have to tune this.
When checking stops on its own
After repeated failures. If a source fails three checks in a row, auto-refresh switches itself off and the source shows Failed: "Syncing paused after repeated failures. Sync now to try again." That prevents a deleted page or a revoked token from burning checks forever. Fix the source and select Sync now to try it once. Sync now doesn't restart the schedule: turn auto-refresh back on with Change schedule.
When the monthly budget runs out. Each workspace has a monthly allowance of scheduled checks, shared across every source that keeps in sync. When it is used up, scheduled checks pause until the allowance resets: "Monthly auto-refresh limit reached. Checks resume next month." Syncs you start by hand are never counted against it.
The Sync schedule window shows how much of the allowance is used once auto-refresh is on.
The budget is shared. Checking thirty rarely-changing pages spends it on nothing; checking your changelog, your docs and your X profile spends it where content actually moves.
Gaps flags a failed sync
When a source stops syncing successfully, it shows Failed on the Sources tab and appears on the Gaps tab as a Failed sync: "The agent stopped reading this source. Fix it in Sources, then sync it again." Open source takes you to its row. Content it indexed before keeps answering until you fix or remove it.