Unverified50% confidenceFactExact time
Resuming from a checkpoint re-executes any LLM calls, API requests or interrupts, which may cause the draft approved by the approver to differ from the draft finally executed.
1
Sources
50%
Confidence
Long-term
Relevance
10/21/2026
First Seen
Sources
Related Entities
Related Claims
Unverifiedrestore.add_input() allows an audit note to be attached during approval, passing the approval reason to the LLM.76% similarUnverifiedThe fix involves reusing already-persisted tool rejection results during the approval resumption process (commit hash d9e04cb).73% similarUnverifiedA status page marked 'Resolved' usually means the service has recovered, but whether orders that failed or were pending during the incident will be automatically retried, and whether they will cause duplicate charges, needs to be verified separately by developers on the application side.71% similarUnverifiedMaking the approval gate a separate graph node (tool_gate) avoids re-executing the work node's LLM call on resume, thereby preventing duplicate billing.69% similarUnverifiedAnother fix is to apply to reviews the same staleness guard as the comment path, requiring the verdict to be newer than the last commit and not already processed, with two independent conditions making the review be treated as processed.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1081278API
curl https://kongchang.com/api/v1/knowledge/claims/1081278MCP
get_claim(id=1081278)