chore: update workflow queues api

[NathanFlurry]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[railway-app]

🚅 Deployed to the rivet-pr-4230 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
ladle	❌ Build Failed (View Logs)	Web	Feb 19, 2026 at 10:40 pm
website	✅ Success (View Logs)	Web	Feb 19, 2026 at 10:08 pm
frontend-cloud	❌ Build Failed (View Logs)	Web	Feb 19, 2026 at 7:45 am
frontend-inspector	❌ Build Failed (View Logs)	Web	Feb 19, 2026 at 7:44 am
mcp-hub	✅ Success (View Logs)	Web	Feb 19, 2026 at 7:44 am

[NathanFlurry]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• fix(rivetkit): fix run workflow teardown #4239
• feat(rivetkit): canInvoke #4237
• chore(rivetkit): make execute generic #4231
• chore: update workflow queues api #4230 👈 (View in Graphite)
• chore: simplify queue api #4229
• refactor(rivetkit): add typed event and queue schemas for actors #4209 : 1 other dependent PR (#4224 )
• feat: configure rivetkit storage path #4233
• chore(rivetkit): migrate file system driver to sqlite #4206
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

PR Review: chore: update workflow queues api

This PR replaces the listen* method family (listen, listenN, listenWithTimeout, listenUntil, listenNWithTimeout, listenNUntil) with a unified ctx.queue.next(name, opts) API. It also removes the workflowQueueName() prefix wrapper, making actor queue names and workflow queue names identical. Overall this is a good API consolidation, but there are a few concerns to address.

---

Critical: History Compatibility

The most significant risk is breaking existing in-flight workflows. Two independent changes affect history replay:

1. History key layout changed. The old listenUntil stored history under ${name} (sleep) and ${name}:message (message). The new executeQueueNext uses ${name}:count, ${name}:deadline, and ${name}:0. Any workflow currently sleeping in a listenUntil or listenWithTimeout will hit HistoryDivergedError on its next run.

2. History marker renamed. LISTEN_HISTORY_MESSAGE_MARKER (__rivetWorkflowListenMessage) → QUEUE_HISTORY_MESSAGE_MARKER (__rivetWorkflowQueueMessage). Entries written by the old code will fall through to the legacy deserialization path in fromHistoryQueueMessage, which recovers the data field but loses id, name, and createdAt. This is probably tolerable but worth confirming.

If any workflows are running in production (or in long-lived tests), they will fail after this deploy. A migration strategy or a compatibility shim for old history entries should be considered.

---

Behavioral Change: Batch Collection

The old listenNUntil accumulated messages iteratively across multiple yield-resume cycles — it would collect one message per run, yield, then collect another. The new queue.next with count > 1 does a single consumeMessages call per run. This means partial batches are only possible if fewer than count messages are already in the queue at the moment of the call, not if they arrive across multiple cycles. This is a subtle but real behavioral difference for patterns that relied on incremental accumulation.

---

waitingForMessages !== undefined vs length > 0

In rivetkit-typescript/packages/workflow-engine/src/index.ts:

-const hasMessages =
-    result.waitingForMessages && result.waitingForMessages.length > 0;
+const hasMessages = result.waitingForMessages !== undefined;

If waitingForMessages is ever an empty array (e.g., from a queue.next with names: []/wildcard match that yields with no specific names), the live executor will enter the message-wait path unnecessarily. The old guard was tighter. Worth verifying whether waitingForMessages: [] is a valid state.

---

Indentation Noise in context.ts

The checkDuplicateName body in WorkflowContextImpl gained an extra level of indentation without a structural change. Similar whitespace drift appears in several test blocks in messages.test.ts. Probably not functional, but adds noise to the diff and may cause lint failures.

---

Minor: history-examples.ts Semantic Equivalence

Replacing listenUntil(name, queue, Date.now() + 300) with queue.next(name, { timeout: 300 }) is semantically equivalent since executeQueueNext converts the relative timeout to an absolute deadline on first run. No issue here, but Date.now() is now called slightly later (inside executeQueueNext rather than at call site). Should be unobservable in practice.

---

Positive Observations

• The unified ctx.queue.next() API is a significant ergonomic improvement — one method replaces six with orthogonal options.
• Removing workflowQueueName() eliminates the impedance mismatch between actor queue keys and workflow message names.
• ctx.queue.send() is a useful addition that was missing before.
• TypeScript type inference for queue body types and event types now flows correctly through the workflow context hierarchy and into loop/join/race callbacks.
• The receiveMessages() driver hook cleanly allows actor-backed workflows to reuse native queue semantics without double-buffering.
• The pendingCompletableMessageIds guard is a good safety mechanism, and the new tests covering it are thorough.
• New expectTypeOf type tests in actor-types.test.ts are a good addition.

---

Summary

The API design is sound and the implementation is well-thought-out. The primary concern before merging is the history compatibility issue for any workflows currently mid-execution. If this is a fresh system or all workflows can be drained/restarted, the risk is low. Otherwise, a compatibility layer for old history entries or a coordinated migration is needed.

[pkg-pr-new]

More templates

• actor-actions
• actor-actions-vercel
• ai-agent
• ai-agent-vercel
• example-ai-and-user-generated-actors-freestyle
• chat-room
• chat-room-vercel
• example-cloudflare-workers
• example-cloudflare-workers-hono
• collaborative-document
• collaborative-document-vercel
• cross-actor-actions
• cross-actor-actions-vercel
• example-cursors
• example-cursors-raw-websocket
• example-cursors-raw-websocket-vercel
• example-cursors-vercel
• custom-serverless
• custom-serverless-vercel
• example-elysia
• example-elysia-vercel
• example-experimental-durable-streams-ai-agent
• example-experimental-durable-streams-ai-agent-vercel
• geo-distributed-database
• geo-distributed-database-vercel
• hello-world
• hello-world-vercel
• example-hono
• hono-react
• hono-react-vercel
• example-hono-vercel
• example-kitchen-sink
• example-kitchen-sink-vercel
• multi-region-vercel
• multiplayer-game
• multiplayer-game-vercel
• native-websockets
• native-websockets-vercel
• next-js
• per-tenant-database
• per-tenant-database-vercel
• example-raw-fetch-handler
• example-raw-fetch-handler-vercel
• example-raw-websocket-handler
• example-raw-websocket-handler-proxy
• example-raw-websocket-handler-proxy-vercel
• example-raw-websocket-handler-vercel
• example-react
• example-react-vercel
• sandbox
• sandbox-coding-agent
• sandbox-coding-agent-vercel
• sandbox-vercel
• scheduling
• scheduling-vercel
• example-sqlite-drizzle
• example-sqlite-raw
• example-sqlite-raw-vercel
• state
• state-vercel
• example-stream
• example-stream-vercel
• example-trpc
• example-trpc-vercel

@rivetkit/cloudflare-workers

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/cloudflare-workers@4230

@rivetkit/framework-base

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/framework-base@4230

@rivetkit/next-js

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/next-js@4230

@rivetkit/react

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/react@4230

rivetkit

pnpm add https://pkg.pr.new/rivet-dev/rivet/rivetkit@4230

@rivetkit/sql-loader

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sql-loader@4230

@rivetkit/sqlite-vfs

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sqlite-vfs@4230

@rivetkit/traces

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/traces@4230

@rivetkit/workflow-engine

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/workflow-engine@4230

@rivetkit/virtual-websocket

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/virtual-websocket@4230

@rivetkit/engine-runner

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner@4230

@rivetkit/engine-runner-protocol

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner-protocol@4230

commit: 67f79b0

[graphite-app]

Merge activity

• Feb 19, 10:44 PM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Feb 19, 10:45 PM UTC: CI is running for this pull request on a draft pull request (#4238) due to your merge queue CI optimization settings.
• Feb 19, 10:45 PM UTC: Merged by the Graphite merge queue via draft PR: #4238.