feat(webapp,clickhouse): return an actionable error instead of a 500 when a runs list query is too expensive by ericallam · Pull Request #4773 · triggerdotdev/trigger.dev

ericallam · 2026-08-25T09:42:02Z

Summary

When a runs list query is too expensive to complete, it now fails with a clear, actionable error instead of a generic 500.

Previously, a runs list query that exceeded ClickHouse resource limits threw an opaque error. On the public runs.list API that surfaced as a retryable 500, so a customer task calling it would keep retrying a query that could never succeed. On the dashboard it rendered as a generic error page with no hint about what to do.

Fix

The ClickHouse client now tags resource-limit failures (memory, time, rows, bytes) with their error type, and the runs repository maps those to a dedicated RunsListQueryError (HTTP 422).

runs.list API returns 422 with a message telling the user to narrow their created_at range, plus an x-should-retry: false header so the SDK does not retry it.
The dashboard runs list (and the errors, scheduled, standard-task, agents, and webhooks list views) render a shared error state with the same guidance, so a too-broad time filter is recoverable by the user.

…when a runs list query is too expensive When a runs list query exceeds ClickHouse resource limits, surface a clear error asking the user to narrow their time range, and stop retrying it. The public runs.list API now returns 422 with a helpful message and an x-should-retry: false header, so the failure is non-fatal for tasks. The dashboard runs list shows the same guidance instead of a generic error page.

changeset-bot · 2026-08-25T09:42:08Z

⚠️ No Changeset found

Latest commit: 4625cf4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

coderabbitai · 2026-08-25T09:43:14Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

Walkthrough

The change detects ClickHouse resource-limit errors and preserves their types through QueryError. The runs repository maps these failures to RunsListQueryError, and the API returns a non-retryable 422 response with an actionable message. A shared RunsListErrorState replaces spinner and inline callout states across runs-list views. Dedicated ClickHouse connections serve runs-list queries. Container tests cover resource-limited and unrestricted queries. A changelog entry documents the behavior.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 25.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 12 functions across 16 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check	⚠️ Warning	The description clearly explains the problem and the implemented fix, but it omits the required issue reference, checklist, Testing section, Changelog section, and Screenshots section from the reposit…	Add the missing template sections. Include the issue reference, complete the checklist, document the test commands and results, add a short changelog entry, and provide screenshots or state that screenshots are not applicable.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely describes the main change: returning an actionable error instead of a 500 for overly expensive runs list queries.

Full details: Description check

Explanation

The description clearly explains the problem and the implemented fix, but it omits the required issue reference, checklist, Testing section, Changelog section, and Screenshots section from the repository template.

✨ Finishing Touches 💡 2

📝 Generate docstrings 💡

Create stacked PR
Commit on current branch

🛠️ Fix failing CI checks 💡

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feature/tri-13475-runs-list-return-an-actionable-error-not-a-500-when-a-query

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

github-actions · 2026-08-25T09:44:19Z

Observability map

As of 4625cf4.

19/100 over 449 measured of 467 entry points (base 19, no change)

What this PR changed

route	base	head	now failing
/api/v1/runs	0	50

FIX FIRST

/api/v1/projects/:projectRef/envvars (sensitive) - auth-boundary, request-context
/auth/sso (sensitive) - auth-boundary, request-context
/_app/orgs/:organizationSlug/settings/team (sensitive) - error-classification, auth-scope, request-context

AUDIT 3 of 50 sensitive mutations record an actor. 47 without one.
CONTEXT 23 of 449 entry points name a tenant on a failure path. 347 appear only here, 39 of them sensitive, in the JSON rather than the fix list.

What the score is made of

CHECKS
  error-classification  182 applicable, 104 pass,   0 sole, global without it 12
  auth-boundary          62 applicable,  57 pass,   0 sole, global without it 16
  auth-scope             19 applicable,  17 pass,   0 sole, global without it 19
  request-context       449 applicable,  23 pass, 245 sole, global without it 64
  audit-trail            50 applicable,   3 pass,   0 sole, not in the score

The score and findings here are report-only and never gate the merge. Separately, a required test suite keeps this tool's symbol and route lists in sync with the code they name, and can fail a pull request that renames or removes a symbol they reference, or that adds the first route with a segment they anticipate. Each failure names the list to edit. The rules and their reasons: internal-packages/observability-map/README.md.

Route the runs list on the task, scheduled, agent, webhook, and error-group pages through the same capped ClickHouse pool as the main runs list, and let a resource-limit failure surface the in-panel error state instead of being swallowed to an empty list or bubbling to a full-page error.

…wait An empty JSX fragment as errorElement trips the no-useless-fragment lint rule. Replace it with a small component that renders null, which handles a runs-list rejection locally on the pagination await so it does not bubble to the route error boundary.

coderabbitai

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

apps/webapp/app/components/runs/v3/RunsListErrorState.tsx (1)

12-17: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Make RunsListErrorState fill the available runs-list region before centering.

The root <div> at Line 12 has no height or flex-growth rule, so items-center only centers inside its content-sized box. Give fixed-height callers a definite height, such as h-full, and let auto-sized flex callers grow before centering.

Source: Coding guidelines

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9fd89371-8ece-4961-9f07-529aa0acd51f

📥 Commits

Reviewing files that changed from the base of the PR and between 4440134 and 524ed61.

📒 Files selected for processing (5)

apps/webapp/app/components/runs/v3/RunsListErrorState.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.agents.$agentParam/route.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.scheduled.$taskParam/route.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.standard.$taskParam/route.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.webhooks.$webhookParam/route.tsx

🚧 Files skipped from review as they are similar to previous changes (1)

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.webhooks.$webhookParam/route.tsx

Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review.

📜 Review details

⏰ Context from checks skipped due to timeout. (32)

GitHub Check: webapp / 🧪 Unit Tests: Webapp (18, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (10, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (23, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (21, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (16, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (17, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (13, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (24, 24)
GitHub Check: e2e-webapp / 🧪 E2E Tests: Webapp (1, 2)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (12, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (2, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (20, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (22, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (11, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (19, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (6, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (15, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (9, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (4, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (7, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (14, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (1, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (8, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (3, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (5, 24)
GitHub Check: internal / 🧪 Unit Tests: Internal
GitHub Check: e2e-webapp / 🧪 E2E Tests: Webapp (2, 2)
GitHub Check: runops-guard / runops-guard
GitHub Check: fk-cascade-guard / fk-cascade-guard
GitHub Check: code-quality / code-quality
GitHub Check: 🛡️ E2E Auth Tests (full)
GitHub Check: Analyze (javascript-typescript)

🧰 Additional context used

📓 Path-based instructions (7)

For dashboard changes, visually verify the running Remix app with Chrome DevTools MCP, using snapshots, screenshots, interaction, and console-message checks as appropriate.

📄 CodeRabbit inference engine (apps/webapp/CLAUDE.md)

Files:

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.standard.$taskParam/route.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.agents.$agentParam/route.tsx
apps/webapp/app/components/runs/v3/RunsListErrorState.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.scheduled.$taskParam/route.tsx

**Prefer static imports over dynamic imports.** Only use dynamic `import()` when:

📄 CodeRabbit inference engine (AGENTS.md)

Files:

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.standard.$taskParam/route.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.agents.$agentParam/route.tsx
apps/webapp/app/components/runs/v3/RunsListErrorState.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.scheduled.$taskParam/route.tsx

Add crumbs as you write code — not just when debugging. Mark lines with

📄 CodeRabbit inference engine (AGENTS.md)

Files:

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.standard.$taskParam/route.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.agents.$agentParam/route.tsx
apps/webapp/app/components/runs/v3/RunsListErrorState.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.scheduled.$taskParam/route.tsx

Use zod for validation in packages/core and apps/webapp

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Files:

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.standard.$taskParam/route.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.agents.$agentParam/route.tsx
apps/webapp/app/components/runs/v3/RunsListErrorState.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.scheduled.$taskParam/route.tsx

Access environment variables through the `env` export of `env.server.ts` instead of directly accessing `process.env`

📄 CodeRabbit inference engine (.cursor/rules/webapp.mdc)

Files:

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.standard.$taskParam/route.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.agents.$agentParam/route.tsx
apps/webapp/app/components/runs/v3/RunsListErrorState.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.scheduled.$taskParam/route.tsx

Use function declarations instead of default exports

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Files:

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.standard.$taskParam/route.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.agents.$agentParam/route.tsx
apps/webapp/app/components/runs/v3/RunsListErrorState.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.scheduled.$taskParam/route.tsx

Use types over interfaces for TypeScript

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Files:

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.standard.$taskParam/route.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.agents.$agentParam/route.tsx
apps/webapp/app/components/runs/v3/RunsListErrorState.tsx
apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.scheduled.$taskParam/route.tsx

🔇 Additional comments (4)

apps/webapp/app/components/runs/v3/RunsListErrorState.tsx (1)

21-28: LGTM!

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.agents.$agentParam/route.tsx (1)

25-29: LGTM!

Also applies to: 100-103, 162-162, 174-179, 354-354, 408-408

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.scheduled.$taskParam/route.tsx (1)

63-67: LGTM!

Also applies to: 151-154, 219-219, 232-237, 388-395

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.tasks.standard.$taskParam/route.tsx (1)

33-37: LGTM!

Also applies to: 111-114, 161-161, 175-180, 284-291

… tuning Every ClickHouse read query now records duration (wall-clock and server-side), rows and bytes read, peak memory usage, an in-flight gauge, and an error counter tagged by ClickHouse error type, all keyed by client and operation. These give the runs-list pool live signal for sizing max_open_connections and the per-query caps instead of one-off query_log snapshots.

…eturning A thrown exception in the query path (e.g. a malformed response or a stream error) bypassed the metrics recording and emitted no error or duration sample. Record an exception-typed error metric before rethrowing so those failures are visible too.

coderabbitai

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

internal-packages/clickhouse/src/client/client.ts (1)
134-140: 🚀 Performance & Scalability | 🟡 Minor | ⚡ Quick win

Use bounded metric attributes.

this.name and req.name have unrestricted string types. The client and operation attributes can create a new Prometheus time series for each value. Remove these attributes, or map them to a closed bounded set, before calling record() and add(). Keep bounded attributes such as status and error_type.
Proposed fix
-    const attributes = { client: this.name, operation };
+    const attributes = {};
...
-      this.queryInFlight.add(1, { client: this.name });
+      this.queryInFlight.add(1);
...
-        .finally(() => this.queryInFlight.add(-1, { client: this.name }));
+        .finally(() => this.queryInFlight.add(-1));
As per coding guidelines, metric attributes must use only enums, booleans, bounded error codes, or bounded shard IDs.

Also applies to: 194-194, 325-325, 378-378, 550-550, 571-571, 681-681

Source: Coding guidelines

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fb2fe487-bbb9-4be8-8944-356929b32901

📥 Commits

Reviewing files that changed from the base of the PR and between b786db5 and 4625cf4.

📒 Files selected for processing (1)

internal-packages/clickhouse/src/client/client.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review.

📜 Review details

⏰ Context from checks skipped due to timeout. (36)

GitHub Check: webapp / 🧪 Unit Tests: Webapp (9, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (19, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (23, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (18, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (14, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (20, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (13, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (15, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (2, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (21, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (24, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (10, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (5, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (6, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (22, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (1, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (17, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (16, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (8, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (7, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (4, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (12, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (11, 24)
GitHub Check: webapp / 🧪 Unit Tests: Webapp (3, 24)
GitHub Check: obsmap / 🧪 Unit Tests: Observability Map
GitHub Check: fk-cascade-guard / fk-cascade-guard
GitHub Check: e2e-webapp / 🧪 E2E Tests: Webapp (1, 2)
GitHub Check: e2e-webapp / 🧪 E2E Tests: Webapp (2, 2)
GitHub Check: typecheck / typecheck
GitHub Check: internal / 🧪 Unit Tests: Internal
GitHub Check: runops-guard / runops-guard
GitHub Check: report
GitHub Check: code-quality / code-quality
GitHub Check: Analyze (javascript-typescript)
GitHub Check: 🛡️ E2E Auth Tests (full)
GitHub Check: 🛡️ E2E Auth Tests (full)

🧰 Additional context used

📓 Path-based instructions (5)

**Prefer static imports over dynamic imports.** Only use dynamic `import()` when:

📄 CodeRabbit inference engine (AGENTS.md)

Files:

internal-packages/clickhouse/src/client/client.ts

Add crumbs as you write code — not just when debugging. Mark lines with

📄 CodeRabbit inference engine (AGENTS.md)

Files:

internal-packages/clickhouse/src/client/client.ts

Use function declarations instead of default exports

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Files:

internal-packages/clickhouse/src/client/client.ts

Use types over interfaces for TypeScript

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Files:

internal-packages/clickhouse/src/client/client.ts

When creating or editing OTEL metrics (counters, histograms, gauges), ensure metric attributes have low cardinality by using only enums, booleans, bounded error codes, or bounded shard IDs

📄 CodeRabbit inference engine (.cursor/rules/otel-metrics.mdc)

Files:

internal-packages/clickhouse/src/client/client.ts

🔇 Additional comments (1)

internal-packages/clickhouse/src/client/client.ts (1)

74-102: Add required development crumbs.

Add // @crumbs`` markers around metric initialization and exception metric recording. Use an existing crumb namespace, or ask before selecting one.

As per coding guidelines, “Add crumbs as you write code.”

Also applies to: 321-324, 546-549, 677-680

Source: Coding guidelines

## Summary 4 new features, 12 improvements, 5 bug fixes. ## Improvements - `trigger.dev deploy` now asks the server whether to build with Depot or the native build server unless `--native-build`, `--depot-build`, or `--local-build` is passed, so the native build server can be rolled out per organization without a CLI change. `--local-bundle` and `--detach` now require `--native-build`. ([#4803](#4803)) - Add an experimental `--local-bundle` deploy flag that runs the install and bundling steps on your machine and uploads only the build output; the image is still built remotely. Useful when your project's install step needs tooling or credentials that only exist locally. ([#4331](#4331)) - Send the CLI version header on all API requests so deployments are attributable to a CLI version ([#4778](#4778)) - A message that arrives mid-turn and is not injected into that turn is now answered as the next turn, instead of being dropped. This is what the `pendingMessages` docs have always described, and it applies to the default too: configuring `pendingMessages` without a `shouldInject` declines every batch, which previously meant every mid-turn message was lost with no error at either end. ([#4795](#4795)) ```ts chat.agent({ id: "my-chat", pendingMessages: { onReceived: ({ message }) => logger.info("arrived mid-turn", { id: message.id }), // Only interrupt once the agent has started calling tools. shouldInject: ({ steps }) => steps.length > 0, }, run: async ({ messages, signal }) => streamText({ model, messages, abortSignal: signal, // Required for injection. Without it nothing injects, and every // mid-turn message is answered as the next turn instead. ...chat.toStreamTextOptions(), }), }); ``` A declined message keeps its place in the queue, so it survives a crash and is answered by whichever run picks the conversation up. An injected one is consumed at the moment it is injected, so it is never also answered as a later turn. - Browser chats now keep the active turn open across page reloads when older completion records are replayed. ([#4643](#4643)) - Add `chat.endAndContinue()` so fully hand-rolled custom chat agents can hand a conversation off to a fresh run on the latest deployed task version while preserving unconsumed Session input. ([#4647](#4647)) - Custom chat agents now validate and parse client data declared with `chat.withClientData({ schema })` before passing it to agent code. ([#4646](#4646)) ## Bug fixes - Fixes a case where a chat could silently lose a message. If a message arrived while the agent was between turns and a stop arrived after it, the cursor the next boot resumed from could point past that message, so it was never answered and no error was raised. This affected `chat.agent`, not just custom agents. ([#4644](#4644)) Fixes a recovered answer being cut off. After a crash the agent replays the message it had not answered yet, but it was replaying the stop that arrived after that message too, so the turn answering it was aborted the moment it began. A stop is now only applied to the turn that was live when it arrived. That holds however the stop got there: sent after the last completed turn, or sent to a chat whose most recent turn was completed by an older version of the SDK. One limitation to know about: the recovered answer is persisted correctly, but a chat page that stayed open across the crash keeps showing the partial answer it had already received. Reload the page to see the full recovered answer. Also fixes a retried send being answered twice. When a send was retried and its idempotency claim was lost, the agent could consume the same message a second time. Custom agent loops can now inspect pending chat input without consuming it, and consume one record at a time, with `chat.messages.hasPending()` and `chat.messages.next()`. Records carry stable identifiers so a redelivery is recognisable. ```ts if (await chat.messages.hasPending()) { const record = await chat.messages.next({ timeoutInSeconds: 0 }); if (record) handle(record.payload); } ``` `hasPending()` answers for messages alone, so a message sitting behind a stop, or behind a record this version of the SDK does not recognise, still reports as pending and is still delivered. Anything the agent has no consumer for is discarded rather than left where it would make every message queued behind it undeliverable. `chat.messages.next()` returning `undefined` means no message became consumable before the timeout. `chat.writeTurnComplete()`'s `sessionInEventId` is the cursor that is safe to resume from, not the sequence of the record the turn answered. It is held back behind any message still waiting to be handled, so a value below the record you just handled is expected. - Fixed a chat agent hanging after an interrupted turn: when a run was killed mid-answer (out of memory, crash, or eviction) and only the one message it was answering was still outstanding, the new run never replied to it. That message is now re-answered on the new run. ([#4768](#4768)) - Fix chat transport discarding the next turn after stopping generation. `skipToTurnComplete` is now reset when a new message or action is sent, so a message sent after `stopGeneration` streams normally instead of leaving the chat stuck in a streaming state. ([#4744](#4744)) - Fixes a message sent while the agent was mid-answer being lost if the run then crashed. The cursor written at the end of each turn could point past a message that had arrived during that turn but had not been answered yet, so the next boot skipped it and no error was raised anywhere. Such a message is now held until a turn actually takes it. ([#4795](#4795)) This also removes the in-memory buffer those messages used to sit in, on both `chat.agent` and `chat.createSession()`, so a message waiting for its turn is durable rather than only present in the worker that received it. ## Server changes These changes affect the self-hosted Docker image and Trigger.dev Cloud: - Self-hosted instances can now disable the admin dashboard and user impersonation entirely. See the self-hosting docs for the new setting. ([#4774](#4774)) - The dashboard has two new themes, Black and White, plus appearance options for stronger colors and underlined links. ([#4547](#4547)) - Deployment logs no longer jump to the bottom while you are reading earlier output. Scroll up to pause auto-scroll, and scroll back down or use the new scroll-to-bottom button in the log header to resume following. ([#4776](#4776)) - Customize the runs list: show, hide, and reorder columns, and add smart columns that pull a value straight out of a run's payload, metadata, or output. Your column choices are saved in the page URL, so you can share a view, bookmark it, or save it straight to your favorites. ([#4652](#4652)) - Stop the browser offering to autofill or save environment variable values as saved credentials. ([#4777](#4777)) - Cut webapp CPU usage by about a quarter on the routes that workers call most, freeing headroom at the same request rate. Detailed event-loop blocking traces are no longer recorded by default, because producing them was itself a large part of that cost. ([#4746](#4746)) - When a runs list or runs.list API request spans too much data to complete, it now returns a clear, actionable error asking you to narrow the time range, instead of failing with a generic error. ([#4773](#4773)) - Improved the performance and reliability of the runs list and the runs.list API, especially for large projects and filtered views. ([#4763](#4763)) - New Vercel connections now get version skew protection turned on automatically, so each run uses the task version its deployment shipped with. Automatic atomic deployments are deprecated and no longer offered when you connect a project, but stay available in your Vercel integration settings. ([#4741](#4741)) - The Staging branch setting now shows an upgrade prompt on plans that don't include a Staging environment, instead of looking editable and then silently doing nothing when saved. ([#4784](#4784)) <details> <summary>Raw changeset output</summary> # Releases ## @trigger.dev/build@4.5.13 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.13` ## trigger.dev@4.5.13 ### Patch Changes - `trigger.dev deploy` now asks the server whether to build with Depot or the native build server unless `--native-build`, `--depot-build`, or `--local-build` is passed, so the native build server can be rolled out per organization without a CLI change. `--local-bundle` and `--detach` now require `--native-build`. ([#4803](#4803)) - Add an experimental `--local-bundle` deploy flag that runs the install and bundling steps on your machine and uploads only the build output; the image is still built remotely. Useful when your project's install step needs tooling or credentials that only exist locally. ([#4331](#4331)) - Send the CLI version header on all API requests so deployments are attributable to a CLI version ([#4778](#4778)) - Updated dependencies: - `@trigger.dev/core@4.5.13` - `@trigger.dev/build@4.5.13` - `@trigger.dev/schema-to-json@4.5.13` ## @trigger.dev/core@4.5.13 ### Patch Changes - `trigger.dev deploy` now asks the server whether to build with Depot or the native build server unless `--native-build`, `--depot-build`, or `--local-build` is passed, so the native build server can be rolled out per organization without a CLI change. `--local-bundle` and `--detach` now require `--native-build`. ([#4803](#4803)) - Add an experimental `--local-bundle` deploy flag that runs the install and bundling steps on your machine and uploads only the build output; the image is still built remotely. Useful when your project's install step needs tooling or credentials that only exist locally. ([#4331](#4331)) - A message that arrives mid-turn and is not injected into that turn is now answered as the next turn, instead of being dropped. This is what the `pendingMessages` docs have always described, and it applies to the default too: configuring `pendingMessages` without a `shouldInject` declines every batch, which previously meant every mid-turn message was lost with no error at either end. ([#4795](#4795)) ```ts chat.agent({ id: "my-chat", pendingMessages: { onReceived: ({ message }) => logger.info("arrived mid-turn", { id: message.id }), // Only interrupt once the agent has started calling tools. shouldInject: ({ steps }) => steps.length > 0, }, run: async ({ messages, signal }) => streamText({ model, messages, abortSignal: signal, // Required for injection. Without it nothing injects, and every // mid-turn message is answered as the next turn instead. ...chat.toStreamTextOptions(), }), }); ``` A declined message keeps its place in the queue, so it survives a crash and is answered by whichever run picks the conversation up. An injected one is consumed at the moment it is injected, so it is never also answered as a later turn. - Fixes a case where a chat could silently lose a message. If a message arrived while the agent was between turns and a stop arrived after it, the cursor the next boot resumed from could point past that message, so it was never answered and no error was raised. This affected `chat.agent`, not just custom agents. ([#4644](#4644)) Fixes a recovered answer being cut off. After a crash the agent replays the message it had not answered yet, but it was replaying the stop that arrived after that message too, so the turn answering it was aborted the moment it began. A stop is now only applied to the turn that was live when it arrived. That holds however the stop got there: sent after the last completed turn, or sent to a chat whose most recent turn was completed by an older version of the SDK. One limitation to know about: the recovered answer is persisted correctly, but a chat page that stayed open across the crash keeps showing the partial answer it had already received. Reload the page to see the full recovered answer. Also fixes a retried send being answered twice. When a send was retried and its idempotency claim was lost, the agent could consume the same message a second time. Custom agent loops can now inspect pending chat input without consuming it, and consume one record at a time, with `chat.messages.hasPending()` and `chat.messages.next()`. Records carry stable identifiers so a redelivery is recognisable. ```ts if (await chat.messages.hasPending()) { const record = await chat.messages.next({ timeoutInSeconds: 0 }); if (record) handle(record.payload); } ``` `hasPending()` answers for messages alone, so a message sitting behind a stop, or behind a record this version of the SDK does not recognise, still reports as pending and is still delivered. Anything the agent has no consumer for is discarded rather than left where it would make every message queued behind it undeliverable. `chat.messages.next()` returning `undefined` means no message became consumable before the timeout. `chat.writeTurnComplete()`'s `sessionInEventId` is the cursor that is safe to resume from, not the sequence of the record the turn answered. It is held back behind any message still waiting to be handled, so a value below the record you just handled is expected. ## @trigger.dev/python@4.5.13 ### Patch Changes - Updated dependencies: - `@trigger.dev/sdk@4.5.13` - `@trigger.dev/core@4.5.13` - `@trigger.dev/build@4.5.13` ## @trigger.dev/react-hooks@4.5.13 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.13` ## @trigger.dev/redis-worker@4.5.13 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.13` ## @trigger.dev/rsc@4.5.13 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.13` ## @trigger.dev/schema-to-json@4.5.13 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.5.13` ## @trigger.dev/sdk@4.5.13 ### Patch Changes - Fixed a chat agent hanging after an interrupted turn: when a run was killed mid-answer (out of memory, crash, or eviction) and only the one message it was answering was still outstanding, the new run never replied to it. That message is now re-answered on the new run. ([#4768](#4768)) - Browser chats now keep the active turn open across page reloads when older completion records are replayed. ([#4643](#4643)) - Add `chat.endAndContinue()` so fully hand-rolled custom chat agents can hand a conversation off to a fresh run on the latest deployed task version while preserving unconsumed Session input. ([#4647](#4647)) - Fix chat transport discarding the next turn after stopping generation. `skipToTurnComplete` is now reset when a new message or action is sent, so a message sent after `stopGeneration` streams normally instead of leaving the chat stuck in a streaming state. ([#4744](#4744)) - Custom chat agents now validate and parse client data declared with `chat.withClientData({ schema })` before passing it to agent code. ([#4646](#4646)) - Fixes a message sent while the agent was mid-answer being lost if the run then crashed. The cursor written at the end of each turn could point past a message that had arrived during that turn but had not been answered yet, so the next boot skipped it and no error was raised anywhere. Such a message is now held until a turn actually takes it. ([#4795](#4795)) This also removes the in-memory buffer those messages used to sit in, on both `chat.agent` and `chat.createSession()`, so a message waiting for its turn is durable rather than only present in the worker that received it. - A message that arrives mid-turn and is not injected into that turn is now answered as the next turn, instead of being dropped. This is what the `pendingMessages` docs have always described, and it applies to the default too: configuring `pendingMessages` without a `shouldInject` declines every batch, which previously meant every mid-turn message was lost with no error at either end. ([#4795](#4795)) ```ts chat.agent({ id: "my-chat", pendingMessages: { onReceived: ({ message }) => logger.info("arrived mid-turn", { id: message.id }), // Only interrupt once the agent has started calling tools. shouldInject: ({ steps }) => steps.length > 0, }, run: async ({ messages, signal }) => streamText({ model, messages, abortSignal: signal, // Required for injection. Without it nothing injects, and every // mid-turn message is answered as the next turn instead. ...chat.toStreamTextOptions(), }), }); ``` A declined message keeps its place in the queue, so it survives a crash and is answered by whichever run picks the conversation up. An injected one is consumed at the moment it is injected, so it is never also answered as a later turn. - Fixes a case where a chat could silently lose a message. If a message arrived while the agent was between turns and a stop arrived after it, the cursor the next boot resumed from could point past that message, so it was never answered and no error was raised. This affected `chat.agent`, not just custom agents. ([#4644](#4644)) Fixes a recovered answer being cut off. After a crash the agent replays the message it had not answered yet, but it was replaying the stop that arrived after that message too, so the turn answering it was aborted the moment it began. A stop is now only applied to the turn that was live when it arrived. That holds however the stop got there: sent after the last completed turn, or sent to a chat whose most recent turn was completed by an older version of the SDK. One limitation to know about: the recovered answer is persisted correctly, but a chat page that stayed open across the crash keeps showing the partial answer it had already received. Reload the page to see the full recovered answer. Also fixes a retried send being answered twice. When a send was retried and its idempotency claim was lost, the agent could consume the same message a second time. Custom agent loops can now inspect pending chat input without consuming it, and consume one record at a time, with `chat.messages.hasPending()` and `chat.messages.next()`. Records carry stable identifiers so a redelivery is recognisable. ```ts if (await chat.messages.hasPending()) { const record = await chat.messages.next({ timeoutInSeconds: 0 }); if (record) handle(record.payload); } ``` `hasPending()` answers for messages alone, so a message sitting behind a stop, or behind a record this version of the SDK does not recognise, still reports as pending and is still delivered. Anything the agent has no consumer for is discarded rather than left where it would make every message queued behind it undeliverable. `chat.messages.next()` returning `undefined` means no message became consumable before the timeout. `chat.writeTurnComplete()`'s `sessionInEventId` is the cursor that is safe to resume from, not the sequence of the record the turn answered. It is held back behind any message still waiting to be handled, so a value below the record you just handled is expected. - Updated dependencies: - `@trigger.dev/core@4.5.13` </details> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

This comment was marked as resolved.

Sign in to view

ericallam marked this pull request as ready for review August 25, 2026 10:34

This comment was marked as resolved.

Sign in to view

coderabbitai Bot reviewed Aug 25, 2026

View reviewed changes

0ski approved these changes Aug 25, 2026

View reviewed changes

This comment was marked as resolved.

Sign in to view

coderabbitai Bot reviewed Aug 25, 2026

View reviewed changes

ericallam merged commit 47ff76d into main Aug 25, 2026
71 of 81 checks passed

ericallam deleted the feature/tri-13475-runs-list-return-an-actionable-error-not-a-500-when-a-query branch August 25, 2026 13:49

github-actions Bot mentioned this pull request Aug 25, 2026

chore: release v4.5.13 #4769

Merged

Navigation Menu

Uh oh!

Uh oh!

feat(webapp,clickhouse): return an actionable error instead of a 500 when a runs list query is too expensive - #4773

feat(webapp,clickhouse): return an actionable error instead of a 500 when a runs list query is too expensive#4773
ericallam merged 5 commits into
mainfrom
feature/tri-13475-runs-list-return-an-actionable-error-not-a-500-when-a-query

ericallam commented Aug 25, 2026

Uh oh!

changeset-bot Bot commented Aug 25, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented Aug 25, 2026 •

edited

Loading

Reviews paused

❌ Failed checks (2 warnings)

Uh oh!

github-actions Bot commented Aug 25, 2026 •

edited

Loading

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

coderabbitai Bot left a comment

Uh oh!

This comment was marked as resolved.

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Uh oh!

Conversation

ericallam commented Aug 25, 2026

Summary

Fix

Uh oh!

changeset-bot Bot commented Aug 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

coderabbitai Bot commented Aug 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviews paused

Walkthrough

❌ Failed checks (2 warnings)

Uh oh!

github-actions Bot commented Aug 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Observability map

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

This comment was marked as resolved.

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

This comment was marked as resolved.

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

changeset-bot Bot commented Aug 25, 2026 •

edited

Loading

coderabbitai Bot commented Aug 25, 2026 •

edited

Loading

github-actions Bot commented Aug 25, 2026 •

edited

Loading