Why your data can look stale

Vyera checks each source on a schedule rather than instantly, so a short delay between a change on a competitor's site and it appearing in your workspace is expected and normal.

How the schedule works

Each source has its own run frequency, set by its module and your plan. A pricing source might run daily, while a careers source might run weekly. You can see when a source last ran, and when it is due to run again, from its detail page.

A source that ran recently but shows no change is not stale. It means the competitor's page has not changed since the last run.

What this does not do

Vyera does not watch pages continuously, and it does not guarantee same-day detection of every change. It does not re-check a source outside its schedule unless you trigger a run yourself, and it does not backfill history for a source added after a change already happened.

When to be concerned

A source is genuinely stale, rather than simply between runs, if its last run date is older than its stated frequency by more than a day or two, or if its status shows as paused or failed. Both of these are visible on the source detail page without needing to contact anyone.

If a source has not run when it was due, the most common cause is that it was paused, either manually or automatically after repeated failures. Resuming it from the source detail page triggers a new run on the usual schedule.

Keeping expectations realistic

Treat Vyera as a record of what changed and when, checked on a predictable cadence, rather than a live feed. For most teams this is sufficient, since decisions are rarely made minute to minute. If your team needs faster detection for a specific source, you can shorten its run frequency from the source settings, within the limits of your plan.