Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: triggerdotdev/trigger.dev
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: triggerdotdev/trigger.dev
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: fix/idempotency-key-catalog-eviction
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 2 commits
  • 11 files changed
  • 1 contributor

Commits on Jul 1, 2026

  1. fix(core,cli): retain idempotency key metadata beyond 1000 keys per run

    The in-process catalog that maps an idempotency key's hash back to its
    original key and scope was a fixed-size LRU capped at 1000 entries. A run
    that created more than 1000 idempotency keys silently evicted the earliest
    mappings, so the SDK sent no idempotencyKeyOptions when triggering. Those
    runs lost their key/scope: ctx.run.idempotencyKey showed only the hash and
    the dashboard/analytics key and scope came back empty.
    
    Replace the LRU with an unbounded in-memory catalog so every key created in
    a run keeps its metadata regardless of count, and clear the catalog at each
    run boundary (via resetExecutionEnvironment) so it does not accumulate across
    warm-start runs that reuse the process.
    matt-aitken committed Jul 1, 2026
    Configuration menu
    Copy the full SHA
    f00d362 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    fdd4a70 View commit details
    Browse the repository at this point in the history
Loading