In short
- Every sync is staged.The new version waits in the background while the old one keeps answering.
- Tested before it goes live.Your test questions run against the update before visitors see it.
- Held when answers get worse.A drop in answer quality, a broken saved test or a mass removal puts the update on hold.
- You make the call.Activate the update anyway, or discard it and keep the previous version.
Your website changes all the time. A redesign, a moved page or a login wall can quietly remove the content your agent relies on. OneType checks every content update first, and keeps your agent's current knowledge live if the update would hurt.
How it works
- OneType re-reads your content and prepares the update in the background.
- Your agent keeps answering from the version that is live now.
- Your agent's test questions run against the update.
- If the update passes, it goes live in one switch.
- If it fails, it is held and you are shown why.
What puts an update on hold
An update is held when your agent would find the right answer noticeably less often: a drop of five points or more in how often the right passage comes up for your test questions. It is also held when any test you saved from a real conversation would break.
A second check looks at size. An update that would remove more than half of a source, when the source has at least ten pages or passages, is held too. That catches the day a site's firewall or a broken page serves nearly empty content.
Review a held update
A held source shows a clear banner, such as "Update on hold: answers got worse in testing". The review shows how often the right passage was found before and after the update, and lists the questions the update would stop answering. Each has a Fix with Q&A button so you can add the answer directly.
Then choose. Activate anyway publishes the update; only owners can do this, and it is written to the audit log. Discard throws the update away and your agent keeps the previous version.
Honest about its limits
The check needs test questions. Until they are ready, an update waits for review, and you can publish it anyway. If the check cannot finish in time, the update goes live so your agent is never stuck, and the source is marked as live but not tested.
The problems it catches
- A redesign that moved or renamed your key pages.
- A firewall or rate limit that turned our reader away.
- A page that suddenly sits behind a login.
- An edit that removed an answer your visitors rely on.
Temporary problems, like a firewall or a rate limit, keep your live text instead of emptying your agent. And the switch to a new version happens in one step, so visitors never see an agent that is half updated.
All of this runs on its own schedule, together with your regular content syncs. You only hear about it when an update needs your decision.