Asset Sync and Notifications
When you edit prompts, documents, vector metadata, or agent definitions in Lyntaris, connected services need to pick up those changes without you restarting everything by hand.
Lyntaris uses an event-driven model: the platform notifies subscribers when relevant assets change. Those subscribers then fetch the latest content—so updates propagate quickly without constant full polling.
What you should know as a user
- You edit in Lyntaris (builder, uploads, prompting, document stores, and similar). Saving triggers internal sync signals.
- Downstream systems (configured by your team) listen for those signals and refresh their caches or ingestion jobs.
- No action is required from end users in the chat UI; this is infrastructure behavior.
If something seems “stale” after a publish, your administrator can verify network access to the Lyntaris host and the integration stack (see Monitoring).
Local development vs production
In development, services often run on localhost with plain HTTP/WebSocket URLs. In production, everything should use your real Lyntaris hostname and TLS (wss://).
The exact WebSocket URL, secrets, and environment variables are deployment-specific. They are documented in the Lyntaris technical documentation for engineers (not duplicated here), so that customer-facing docs stay stable while your stack evolves.
Related
- Uploads — user-facing upload flows.
- Vector Databases (Document Stores) — how document stores fit the product.
- Data Processing — processing pipelines in the UI.
For WebSocket paths, authentication, event payloads, and subscriber behavior on your stack, use the integration or deployment guide supplied with your Lyntaris rollout (your administrator or Lyntaris support can provide the current reference for your environment).