Whose restored reply draft is this? submitted, original target and source binding

Restored text is not a receipt and may still belong to the earlier target

Native replies load per-workbench local records, verify saved source and restore text, target and requestID. Explicit submitted=false denotes an unsent draft; missing/unclear state conservatively restores pending. The target can differ from current selection, with prepare prompting review of the earlier draft. Visible text proves neither server receipt nor authority for a new target.

Different from pending receipts and material retention

Receipts inspect attempted writes; retention maps review material. Here local pre-submit restoration and its source/selection relationship matter. No file is edited/deleted, and no cloud draft/sync/background sender is added.

Check Verified scope Manual review Not established
Local read Size/decode/source URL conditions Failure/original retained record Silently discard bad files and send
Source match saved.source must match Actual source/state Same workbench name means same source
Restored fields Text/target/requestID together Original target/current selection Text belongs to newly opened task
submitted=false Unsent draft branch Persistence/current authority Server recorded or approved
Missing submitted Conservative pending restoration Original check flow Definitely unsent, safely retry
Prepare Fresh target read/change notice Status/next/original target Old local version always valid
Unreadable record Blocked, original retained Actual error/maintenance Rename/delete markers to bypass
Editorial archive Draft/submit/receipt separated Minimal authorized material/version Permanent archive/cloud relay

Synthetic restoration review

Task B is selected, but restored targetID identifies earlier task A. Do not reinterpret A’s text as B’s approval or silently change ownership. Review original/latest target; unknown submitted cannot be filled false.

Saved drafts remain local. Failure notices preserving current-page input are not backup guarantees. Original canSend/source/target/4000-Unicode-scalar conditions remain; no internal-file bypass instructions are supplied.

FAQ

Does restored text mean service receipt?

No. Draft, pending submit and recorded differ.

Must a draft belong to the clicked task?

No. It can restore an earlier item; inspect target/notices.

Does absent submitted mean false?

Current restoration conservatively treats it pending, not definitely unsent.

Do drafts automatically transfer to a changed source?

Do not infer that. Source checks can block while retaining originals.

Is a local draft permanent cloud backup?

No cloud sync/retention/restore SLA is added.

Can internal file edits unlock sending?

Do not bypass guards or fabricate state. Use actual source/target and existing maintenance.

Reading and source

Pending/receipts · Material retention · Target/context · Start · Privacy

Restore/prepare/preserveDraft/canSend · PendingReply fields