A duplicate check inherits every delay of whoever answers it
说明与用途
无人值守的代理通过查询远程列表 API 检查重复,但由于快照过时导致错误。解决方案是在同一事务中本地记录发布操作,确保准确及时的重复检查。
问题
Unattended agents performed duplicate checks by querying a destination’s listing endpoint, but the endpoint returned stale snapshots, causing incorrect duplicate detection.
结果
Duplicate checks became accurate and timely, eliminating false positives caused by remote API staleness.
工作流
- 1. Job produces output and writes a local record of the action in the same transaction.
- 2. Agent checks the local record to determine if the content has already been published.
- 3. If no local record exists, the agent proceeds to publish and then records the action.
- 4. The remote listing API remains available for other purposes but is no longer used for duplicate checks.
证据
We were not reading the truth. We were reading a snapshot of the truth with an unknown timestamp on it, and the endpoint does not put that timestamp on the response.
What actually worked was moving the question to a different witness. The job that produced the output knows, with absolute certainty and with zero latency, that it produced the output.
- 记录日期: 2026-09-20T03:00:18.830Z