When scans run and the weekly report

A knowledge base rots on a schedule, so TidyKB checks it on one. Everything about when things happen comes from three settings on the Scan schedule page: your time zone, the day of the week for the report, and the hour.

One setting drives everything

Pick a time zone from the full IANA list — Europe/Berlin, America/New_York. New workspaces start on UTC, and the page offers your browser's zone until you have chosen.

Then pick the weekday and hour your weekly report should land. Everything else is derived from that single time:

Times are wall-clock times in your zone, worked out from the calendar rather than by adding seven days to the last run. Across a daylight-saving change a weekly job is 167 or 169 hours apart, not 168, so adding a week would drift an hour a year and can fire twice in the week the clocks go back. A 07:00 report stays at 07:00.

The page prints the next scan and the next report as real dates and times, so you can check you set what you meant.

The weekly full scan

Every paid plan gets a full scan once a week: every category, folder and article, in every language your portal serves, followed by a link check and all eleven rules. It is the scan that produces the totals and the health score on your dashboard.

The daily top-up on Pro

On Pro, TidyKB also runs a daily scan between the weekly ones. It re-reads only the articles Freshdesk reports as changed since the last scan and refreshes their findings, which is why it is cheap enough to run every day.

A top-up has no score of its own, and because it did not look at everything it never concludes that an article is gone — see what a scan refuses to claim. Any scan on a given day counts as that day's top-up, so the weekly full scan never costs you a daily one as well.

The weekly report

The report is the score, what broke since last week and what was fixed, in an email short enough to read on a phone and forward to a manager.

On the same settings page you can switch it off, and you can list up to ten addresses to send it to; leave the list empty and it goes to the members of your workspace. The scan that feeds it runs four hours before it, so the numbers are from that morning rather than from last week.

A trend between two scans is only shown when both measured the same set of checks. When they did not — a language appeared, or one scan was clipped by your plan's article limit — TidyKB shows a dash and one line saying why, rather than a difference that would not mean anything.

Scanning on demand

Scan now, on the health scan page, starts a full scan immediately. It counts as that day's run, so it costs you nothing extra.

When a scan does not run

The scheduler skips a workspace, rather than piling up work, when:

• The plan has no private scan. The free plan includes the public audit only.
• The connection is not working. A failed or untested connection is never scanned; fix it on the connection page.
• A scan is already queued or running for that connection. Only one at a time, ever.
• It is already up to date for this occurrence.
• You asked too soon. A manual scan has a five-minute cooldown after the previous one.
• It has already failed three times for the same due occurrence, an hour apart. The workspace then waits for the next occurrence instead of hammering a broken connection.

Freshdesk and Freddy are trademarks of Freshworks Inc. TidyKB is an independent product and is not affiliated with, endorsed or sponsored by any company named on this page.