Veti history, queue and recovery
Find history, observe running work, queue messages and inspect uncertain outcomes before repeating.
Platform · VetConnect · Last verified:
Platform and VetConnect carry the same clinical work with different chat layouts. Select account, clinic and conversation first. Closing a surface, switching conversations and stopping work are different actions.
Conversation and history
New Chat may start as a local draft; the first accepted message creates a persistent conversation. Open history and load older pages when needed. Missing from a filter/search does not prove deletion.
Archived conversations remain readable; use offered Unarchive before sending. Titles/previews are not complete history. Unsent text may return within its scope; do not assume it transfers after account/clinic changes.
Running work and queue
Add to queue waits behind current work. Stop and send intends to stop it and start the next message; it does not reverse committed results. Inspect queued/paused state in that conversation. Copying a message into a new chat may create new work.
Expanding Platform's panel moves the existing conversation without sending. Closing/backgrounding mobile may leave accepted server work running. Reopen the same conversation and read current state.
Attention and read state
History may distinguish Needs attention, pending approval and uncertainty. Inspect opens a proposal without applying it. Mark as read neither approves nor resolves uncertainty. Archived pending work remains readable; archive state changes no action outcome.
Disconnection and retry
- Observe reconnect/current work in the same conversation after interruption.
- Sending again differs from rereading an accepted reply.
- Check the exact message/work covered by an offered retry.
- For uncertain money, stock, administration or appointments, read target/history.
- Uncertain outcome proves neither success nor failure; do not begin another write.
Assess success prose together with action outcome and target record. A failure does not make repeated approval safe. Review actions, troubleshooting.
Synthetic check
Send a product question, switch panel/page or conversation during work, and verify the same result/context on return. Separately verify queue/read/inspect controls do not themselves write clinical data. Live model responses and screen behavior need separate acceptance evidence.