Search Center

Keep Search Center answers current

A changed source moving through a scheduled capture, dataset refresh, and answer verification
A changed source moving through a scheduled capture, dataset refresh, and answer verification

A Search Center reads from its connected memory dataset. Updating a website page does not update the answer until the relevant capture job processes the new content.

Match the schedule to the source

Open the data capture job, choose Edit properties, and use Choose frequency to execute under Schedule.

Supported intervals are Every hour, Every 4 hours, Every 8 hours, Every 16 hours, Every 24 hours, Every 3 days, Every 7 days, and Never.

Choose by the cost of stale information rather than by a desire for the shortest interval.

SourcePractical consideration
Product availabilityMay require a short supported interval if the page changes often
DocumentationDaily or weekly may fit, depending on release cadence
Policies and manualsA longer interval may fit stable material
Controlled launch updateA manual Run can provide a known refresh point
Seekdown's capture schedule dropdown showing the available frequencies
Seekdown's capture schedule dropdown showing the available frequencies

Verify a real change

Use a controlled fact whose old and new values are easy to distinguish.

  1. Record the current Search Center answer and cited page.
  2. Update the authoritative source.
  3. Wait for the scheduled job or use Run.
  4. Confirm the capture job completes without an error.
  5. Inspect the dataset record for the new value.
  6. Repeat the same Search Center question.
  7. Confirm the answer and source now reflect the changed page.

This separates capture delay from retrieval or answer problems.

Handle removals and conflicts

When a page is retired, confirm that its obsolete record no longer affects results. If two live pages disagree, fix or exclude one before testing the Search Center again.

Scheduled capture does not establish which source owns a fact. Document that ownership for pricing, security, compatibility, policies, and other change-sensitive topics.

Maintain a small regression set

Keep one or two questions for each important content area. Rerun only the affected group after routine changes, then run the complete set before a major release or dataset-scope change.

Freshness is demonstrated by the source record and repeated answer, not by the schedule setting alone.