Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Explicit support requests need alert-level idempotency, not issue-existence dedupe
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
Do not deduplicate an explicit support request solely by whether a support issue already exists. Existing issues may be active, resolved, or silenced. Reactivate the support episode transactionally, update its current blocked step, then claim the outbound alert with a separate durable idempotency key scoped to the workflow and a bounded server-time window. Only a newly claimed event should route and send; replays may return success without duplicating the alert.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review