Changing knowledge after campaign start
The knowledge state is captured at campaign start, so knowledge changes do not apply retroactively. This article shows how to update content anyway.
Last reviewed: 2026-07-22
Knowledge after the campaign start
When a campaign starts, Nexcal captures a versioned campaign state. This includes, among other things, the conversation strategy, the result fields and the approved knowledge at the time of start. This start state keeps a running campaign reproducible and traceable. For exactly what is saved, see what is saved at campaign start.
Why changes do not apply retroactively
Because the knowledge state is captured at start, later changes to knowledge do not apply retroactively to campaigns that have already started. This protects against unintended changes during runtime and ensures that a campaign's results match the original factual basis. For why campaign settings are locked after start, see why campaign settings are locked after start.
How to update knowledge anyway
If you want to use changed content in production conversations, there are different paths depending on the situation:
- Update the knowledge for future campaigns so that new starts use the current factual basis.
- Consider whether the desired change warrants a new campaign.
- Use test calls to check revised content before a production start.
What to keep in mind
If you update the global company context, this affects all future campaigns. Campaign-specific content affects only the respective campaign. In both cases, keep your content free of contradictions. For guidance, see avoiding outdated or conflicting content.
Hinweis: Plan knowledge changes deliberately. Because the start state is preserved, updates take effect only for newly started campaigns.