github-featured/triggerdotdev--trigger.dev

Files

T

History

Eric Allam 8003923598 feat(server): Gracefully handle oversized batch items instead of aborting the stream (#3137 )

Gracefully handle oversized batch items instead of aborting the stream.

When an NDJSON batch item exceeds the maximum size, the parser now emits
an error marker instead of throwing, allowing the batch to seal
normally. The oversized item becomes a pre-failed run with
`PAYLOAD_TOO_LARGE` error code, while other items in the batch process
successfully. This prevents `batchTriggerAndWait` from seeing connection
errors and retrying with exponential backoff.

Also fixes the NDJSON parser not consuming the remainder of an oversized
line split across multiple chunks, which caused "Invalid JSON" errors on
subsequent lines.

2026-02-27 10:11:42 +00:00

.gitkeep

feat: unified GitHub release, server change tracking, and enhanced release PR (#3085 )

2026-02-25 13:54:19 +00:00

batch-queue-perf-fixes.md

fix(batch-queue): speed up batch queue processing by disabling cooloff and fixing retry race (#3079 )

2026-02-25 17:33:01 +00:00

fix-blocking-waitpoint-race-condition.md

fix(engine) prevent MVCC race in blockRunWithWaitpoint pending check (#3075 )

2026-02-25 17:41:50 +00:00

fix-dispatch-shard-tenant-based.md

feat(batch-queue): two-level tenant dispatch for fair queue (#3133 )

2026-02-26 13:07:27 +00:00

fix-metrics-dashboard-chart-bugs.md

Query fixes: stale widget fix, multiple series colors mismatch (#3126 )

2026-02-25 15:50:17 +00:00

graceful-oversized-batch-items.md

feat(server): Gracefully handle oversized batch items instead of aborting the stream (#3137 )

2026-02-27 10:11:42 +00:00

README.md

feat: unified GitHub release, server change tracking, and enhanced release PR (#3085 )

2026-02-25 13:54:19 +00:00

require-admin-during-impersonation.md

feat(webapp): require the user is an admin during an impersonation session (#3078 )

2026-02-25 16:07:10 +00:00

README.md

Server Changes

This directory tracks changes to server-only components (webapp, supervisor, coordinator, etc.) that are not captured by changesets. Changesets only track published npm packages — server changes would otherwise go undocumented.

When to add a file

Server-only PRs: If your PR only changes apps/webapp/, apps/supervisor/, apps/coordinator/, or other server components (and does NOT change anything in packages/), add a .server-changes/ file.

Mixed PRs (both packages and server): Just add a changeset as usual. No .server-changes/ file needed — the changeset covers it.

Package-only PRs: Just add a changeset as usual.

File format

Create a markdown file with a descriptive name:

.server-changes/fix-batch-queue-stalls.md

With this format:

---
area: webapp
type: fix
---

Speed up batch queue processing by removing stalls and fixing retry race

Fields

area (required): webapp | supervisor | coordinator | kubernetes-provider | docker-provider
type (required): feature | fix | improvement | breaking

Description

The body text (below the frontmatter) is a one-line description of the change. Keep it concise — it will appear in release notes.

Lifecycle

Engineer adds a .server-changes/ file in their PR
Files accumulate on main as PRs merge
The changeset release PR includes these in its summary
After the release merges, CI cleans up the consumed files

Examples

New feature:

---
area: webapp
type: feature
---

TRQL query language and the Query page

Bug fix:

---
area: webapp
type: fix
---

Fix schedule limit counting for orgs with custom limits

Improvement:

---
area: webapp
type: improvement
---

Use the replica for API auth queries to reduce primary load