Skip to content

durable async execution (idempotency, retries, DLQ, replay) #23

Description

@ashupednekar

Summary

Add durable execution semantics for async invocations (idempotency, retries, DLQ, replay).

Motivation

Current async flow lacks strong guarantees for duplicate suppression, retry behavior, and operator-driven recovery.

Proposal

  • Add idempotency key support at ingestor entrypoints.
  • Define retry policy (max attempts, backoff, terminal failure).
  • Add dead-letter subject/stream per project.
  • Add replay tool/API for DLQ messages.

Acceptance criteria

  • Duplicate requests with same key are deduplicated within configured window.
  • Failed async invocations are retried and then moved to DLQ.
  • DLQ replay path is documented and tested.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/ingestorIngestor request and broker flowarea/runtimeRuntime components and language runtimesenhancementNew feature or requestpriority/p1High priority

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions