# Inngest v1.37.0 - Product: Inngest (https://whatsnew.fyi/product/inngest) - Vendor: Inngest - Date: 2026-07-14 - Version: v1.37.0 - Original notes: https://github.com/inngest/inngest/releases/tag/v1.37.0 - Permalink: https://whatsnew.fyi/product/inngest/releases/v1.37.0 What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog. Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'. --- - **added** — Add v2 REST scoring endpoint for recording named scores against function runs or individual steps - **changed** — Improve error response copy to better identify when errors do not come from the SDK but from intermediary proxies or app timeouts - **fixed** — Display errored attempts without step as Function Error rather than Finalization in the trace view - **added** — Extract granular token usage and request parameter information from extended traces for AI Metadata - **changed** — Reduce sleep queue item payload size by approximately 30% - **fixed** — Fix race condition that could cause a completed step to requeue despite already idempotently saving the outcome - **fixed** — Remove duplicate finalization span on errored runs in the trace view - **fixed** — Prevent dev server finalization group spans from duplicating in the trace UI when finalization request failed and was retried - **changed** — Make pause requeue extension configurable - **added** — Return lease usage from Constraint API lifecycle operations - **removed** — Remove run-details-v4 flag and legacy RunDetailsV3, always render V4 ##### Release Notes - [#4453](https://github.com/inngest/inngest/pull/4453) feat(api): add v2 score endpoint Adds a v2 REST scoring endpoint for recording named scores against a function run or individual steps in a run. This `POST /v2/runs/{runId}/scores` with body: ```json [ { "name": "accuracy", "value": 0.95, "stepId": "step 1" } ] ``` Scores are run scoped when `stepId` is omitted. Score values can be a number or boolean. Scores can be submitted in batches of up to 100. Experiment scores are supported at run level only (I copied this from the sdk, shout if we don't want to support this in the api) like so: ```json [ { "name": "accuracy", "value": 0.95, "experiment": { "id": "model-routing", "variant": "baseline" } } ] ``` - [#4566](https://github.com/inngest/inngest/pull/4566) fix(execution): improve copy for error responses that do not come from the SDK Augment responses to better identify when error responses do not come the SDK but rather intermediary proxies or app timeouts. - [#4571](https://github.com/inngest/inngest/pull/4571) fix: Display errored attempts without step as `Function Error` rather than Finalization Errored attempts that never resolved to a step are displayed as "Function error" rather than "Finalization" in the trace view. - [#4572](https://github.com/inngest/inngest/pull/4572) feat: bring AI Metadata extraction from extended traces to parity with JS SDK Extract granular token usage and request parameter information from extended traces for AI Metadata - [#4591](https://github.com/inngest/inngest/pull/4591) perf: reduce sleep queue item payload size Reduces the queue memory footprint of sleeps by ~30%. - [#4593](https://github.com/inngest/inngest/pull/4593) fix: lease race causing wasted work Fix race condition that could cause a completed step to requeue, despite already idempotently saving the outcome - [#4598](https://github.com/inngest/inngest/pull/4598) fix(tracing): drop duplicate finalization span on errored runs Errored runs no longer show a duplicate "Finalization" span in the trace view when every attempt failed before the SDK responded. - [#4600](https://github.com/inngest/inngest/pull/4600) fix(tracing): stop dev server finalization group spans from duplicating in the trace UI Dev server: runs whose finalization request failed and was retried no longer show a duplicate "Finalization" span in the trace view. ##### Migration Notes - [#4597](https://github.com/inngest/inngest/pull/4597) refactor(ui): decompose traceRollup into focused helpers 🤖 Generated with [Claude Code](https://claude.com/claude-code) - [#4598](https://github.com/inngest/inngest/pull/4598) fix(tracing): drop duplicate finalization span on errored runs 🤖 Generated with [Claude Code](https://claude.com/claude-code) - [#4600](https://github.com/inngest/inngest/pull/4600) fix(tracing): stop dev server finalization group spans from duplicating in the trace UI 🤖 Generated with [Claude Code](https://claude.com/claude-code) - [#4603](https://github.com/inngest/inngest/pull/4603) test(constraintapi): add Redis Lua compatibility regression None ## Validation - `go test ./pkg/constraintapi` - `go test ./tests/execution/queue -run 'TestLuaCompatibility/Basic Valkey/constraint API accepts empty usage arrays' -count=1 -v` - `go test ./tests/execution/queue -run 'TestLuaCompatibility/Basic Garnet/constraint API accepts empty usage arrays' -count=1 -v` - Copied the moved regression case onto merge base `fda3771de` and confirmed the Valkey run fails for acquire, extend, and release with `json: cannot unmarshal object into Go struct field ... cu`. ##### Changelog ###### 🚀 Features - *(queue)* Make pause requeue extension configurable (#4569) - *(constraintapi)* Return lease usage from lifecycle ops (#4596) - Bring AI Metadata extraction from extended traces to parity with JS _[Truncated at 4000 characters — full notes: https://github.com/inngest/inngest/releases/tag/v1.37.0]_