Correct a Mistake

Correct an unsaved draft before saving, or correct a saved record and reopen its history. The right path depends on whether anything was saved yet.

What you'll accomplish

Replace a wrong detail with the right one, save the reviewed change, and see the corrected record. You finish knowing whether you changed a draft or a saved record, and what remains available if the correction cannot be completed.

Before you start

  • Owner or Editor access to the farm. Readers cannot save or correct records.
  • The correct detail in hand: the date, identifier, group, description, or amount.
  • A data connection to save. Offline approvals are refused rather than queued.

Correct an unsaved draft

Nothing is saved until you approve the proposal, so a draft correction stays inside the same conversation.

  1. In the draft proposal, choose Change, or send a plain follow-up such as "Actually, yesterday."
  2. Check the revised proposal. The message box shows Changing: {record} · {date} while you point at a particular draft.
  3. Choose Save record when the revised details are right, or Cancel to leave it unsaved.

The old draft becomes a Replaced by a correction receipt that links forward. The revised draft still needs your approval. If the replacement needs more detail, answer the question; if Ranch.Bot cannot prepare one, choose Try again in the same message box.

A question or an unrelated note is treated as a question or a new event, not an edit. If the farm's assistant access or this conversation's consent setting turns off while a change is prepared, the correction is cancelled and nothing is saved. There is nothing to retry, and the replaced draft cannot be saved again.

Correct a saved record

  1. Find the saved record in Records or from a conversation link. If it is linked to an animal, you can also open it from that animal's detail page. For group events, browse Records or ask in Chats. See Find an animal's or group's history.
  2. Describe the correction in Chats. For example: "The movement on August 23 went to East pasture, not West pasture."
  3. Review the proposed update. Check every identifier, date, and description, including details you did not ask to change.
  4. Choose Save changes.
  5. Reopen the record and check the corrected details.

If Ranch.Bot cannot retrieve the exact saved record, clarify which record you mean instead of approving a different one. A saved birth has its own reviewed correction. Open the birth record and use Correct birth or Mark entered in error instead of editing it like an ordinary record.

Undo a recent change, when offered

Undo is offered for some recent changes. It is not a promise that every change can be reversed.

  1. Open the record's Recent Changes, or Change History for the farm.
  2. Choose Undo on the change you need to reverse.
  3. Review the captured farm, change, and time in the dialog.
  4. Confirm, or choose Cancel to stop.
  5. If the result is still unknown, you can choose Close. Review Undo status opens it again.

The dialog shows "This change was undone." only after Ranch.Bot confirms the reversal. Choose View updated history to see the change. If the history does not load, the Undo still counts. Retry history only reloads the list; it does not undo anything again.

Undo is available to Owners and Editors. A group update that adds animals cannot be undone; the confirmation warns you before you save it. Changes saved through the CLI or MCP may not offer Undo in Change History. A whole birth cannot be undone.

How you know it worked

  • A draft correction ends with a saved-record receipt, not just a revised card.
  • A saved-record correction shows the new proposal saved and the record now displays the corrected details and date.
  • An Undo ends with "This change was undone." Open View updated history or the record to see the result.
  • The corrected history stays understandable: the replacement is linked and the original change is not silently rewritten.

If something goes wrong

The save outcome is unknown. Reopen the record or conversation and use Check status before saving again. A lost connection or an error message does not prove the save failed. Do not create a duplicate record to fix it.

Undo is still unknown. Use Check status or Contact support. An unanswered check does not prove the change was not undone. Do not choose Undo again while the outcome is uncertain. If you close the dialog or reload the same tab, Review Undo status opens it again.

Undo was refused. Read the reason. The dialog says whether this is an access problem or a change that cannot be reversed, and points you to a correction or support. Try again appears only when the request was refused before it was sent.

The wrong animal or group is attached. Cancel or correct the proposal before saving. If an identifier is ambiguous, clarify instead of approving a substitute. Do not create a second animal merely to fix an identifier.

The record was saved through another tool. CLI and MCP writes run directly under your permissions and may not offer an in-app Undo. Correct the record through the same surface you used, then check the in-app history.

The record is a birth. Open the birth record and use Correct birth or Mark entered in error. Do not edit, delete, or undo it like an ordinary record.