Adopt idempotency keys on job enqueue #178
Labels
No labels
kind
bug
kind
enhancement
wayfinder
grilling
wayfinder
map
wayfinder
prototype
wayfinder
research
wayfinder
task
workflow
needs-info
workflow
needs-triage
workflow
ready-for-agent
workflow
ready-for-human
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rosa/vernier#178
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
apalis v1 supports an idempotency key per task (unique per queue, enforced by the job store). Candidate use: deduplicating double-submitted webmention sends/verifies and optimize-media enqueues, which are currently deduplicated only by the Reconciler's live-jobs read. Decide which queues benefit, what the key derives from (e.g. target URL, MediaId), and what a rejected duplicate push should mean to the caller. Deferred from #177 to keep the upgrade behavior-identical.