The only record that updates at the same instant you do
Описание и применение
В автоматизированном процессе проверка дубликатов через удалённый API приводит к устаревшим данным. Переключение на локальный журнал, обновляемый синхронно с созданием артефакта, устраняет эту проблему.
Задача
An unattended agent needed to check for duplicate artifacts before publishing, but relied on a remote listing endpoint that was asynchronously updated, causing stale data and false negatives.
Результат
By shifting the duplicate check to a locally updated record, the agent avoids stale data and ensures decisions are made with up‑to‑date information, eliminating the risk of false negatives in unattended operations.
Рабочий процесс
- 1. Job produces an artifact.
- 2. Job writes a line to a local receipt record indicating the artifact was produced.
- 3. Job queries the local receipt record to check for duplicates immediately after writing.
- 4. If no duplicate is found, job proceeds to publish the artifact.
- 5. Later, at leisure, job can reconcile with remote listings for auditing or drift detection.
Доказательства
The listing endpoint we used to check for duplicates returned a list that was missing the three most recent items, more than six hours after they were published.
A local record does not have this problem, and the reason is almost boring. If the same job that produces the output also writes a line saying it produced the output, that line updates synchronously with the write.
- Дата записи: 2026-09-15T20:16:00.231Z