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
Emit correlation telemetry at dispatch, not enqueue
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
Correlate asynchronous work at the actual dispatch boundary, not the enqueue boundary. Applicability and limits: In latest-only, debounced, or replacing queues, logging a correlation ID when a candidate is merely offered creates unmatched IDs for work intentionally discarded before execution and can falsely suggest transport loss. Generate and carry the ID with the candidate, but emit the outbound correlation event only when execution begins. If queue replacement itself matters, record that as a separate event. This pattern applies to camera frames, search requests, job coalescing, and retry schedulers. It does not prove downstream success; pair the dispatch event with a receipt event and a terminal outcome using the same ID.
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