v4.6.3

triggerdotdev/trigger.devv4.6.3Sep 17, 2026by github-actions[bot]

Upgrading?

AI Summary

Continues to address the Zod bug warning while adding improvements to error handling, cron schedule warnings, and chat agent model context management.

Key Highlights

  • Warning remains for Zod bug in versions 4.6.0 through 4.6.3
  • Error cause chains are now captured and displayed in dashboard and alerts
  • Shows how to override the default cron window in schedule policy warnings
  • Optimizes chat agent context by excluding summarized steps after compaction

New Features

  • Capture and display thrown error cause chains for debugging
  • Show how to override default cron window in schedule policy warnings
  • Keep summarized assistant steps out of future chat.agent() model context

Full Release Notes

# trigger.dev v4.6.3

> [!WARNING]
> A Zod import bug in versions 4.6.0 through 4.6.3 can cause warm starts to fail and delay runs by approximately five minutes when using npm with Zod 3 pinned in `package.json`. Cold starts are unaffected by this bug. No data has been lost.
>
> Redeploy with `npx trigger.dev@latest deploy`, or update your pinned CLI version to **4.6.4 or later** and redeploy. [Read about the fix](https://trigger.dev/changelog/v4-6-4).

## Upgrade

```sh
npx trigger.dev@latest update  # npm
pnpm dlx trigger.dev@latest update  # pnpm
yarn dlx trigger.dev@latest update  # yarn
bunx trigger.dev@latest update  # bun
```

Self-hosted Docker image: [`ghcr.io/triggerdotdev/trigger.dev:v4.6.3`](https://github.com/triggerdotdev/trigger.dev/pkgs/container/trigger.dev/1260749993?tag=v4.6.3)

## Release notes

Read the full release notes: https://trigger.dev/changelog/v4-6-3

## What's changed

## Improvements
- Show how to override the default cron window in schedule policy warnings. ([`630eb75d1`](https://github.com/triggerdotdev/trigger.dev/commit/630eb75d1a83a1474d45f155780147ba90cda8e8))
- Thrown error `cause` chains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message. ([`4f36f614b`](https://github.com/triggerdotdev/trigger.dev/commit/4f36f614b7937f9419900bef4080c42cd34b292b))
  
  ```ts
  throw new Error("Could not sync the customer", { cause: originalError });
  ```
  
  The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the `error` of API and realtime run records as a `causes` array, and `triggerAndWait` and `triggerAndSubscribe` rebuild it as a native `cause` on the error they hand back, so `err.cause` works in your own catch blocks.
- Keep summarized assistant steps and tool results out of future `chat.agent()` model context after inner compaction, while preserving the full visible conversation. ([`fc77bfc9a`](https://github.com/triggerdotdev/trigger.dev/commit/fc77bfc9a2005159b64f0f51777f4ab8e79ba6a9))

## All packages: v4.6.3

@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev

## Contributors

Chris Arderne, Wes Mason, Eric Allam, github-actions[bot], @Mariefay, Matt Aitken, @d-cs

**Full changelog**: https://github.com/triggerdotdev/trigger.dev/compare/v4.6.2...v4.6.3

Related Repositories