DO NOT MERGE: queue diagnose

[abcxff]

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-5050 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
frontend-inspector	❌ Build Failed (View Logs)	Web	May 13, 2026 at 2:59 am
frontend-cloud	❌ Build Failed (View Logs)	Web	May 13, 2026 at 2:57 am
kitchen-sink	❌ Build Failed (View Logs)	Web	May 13, 2026 at 2:57 am
ladle	❌ Build Failed (View Logs)	Web	May 12, 2026 at 5:53 pm
mcp-hub	✅ Success (View Logs)	Web	May 12, 2026 at 5:48 pm
website	❌ Build Failed (View Logs)	Web	May 12, 2026 at 5:47 pm

[abcxff]

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

• DO NOT MERGE: queue diagnose #5050 👈 (View in Graphite)
• fix(rivetkit): keep actor alive while workflow waits for queue messages #5052
• [slop]fix(workflow-engine): only commit step state after success #5010
• temp: fix wasm-pack #5048
• fix(rivetkit): bind methods through createWriteThroughProxy #4987
• feat(rivetkit): add ConnectionMap readonly Map wrapper for actor connections #5047
• fix(rivetkit-core): chunk apply_batch puts/deletes at 128 #5046
• fix(pegboard): validate drain_grace_period < request_lifespan #4998
• chore(rivetkit): log inspector errors + standardize pino errorKey error #4986
• fix(rivetkit): remove async drizzle db proxy #4984 : 2 other dependent PRs (#4985 , #4991 )
• main

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

[claude]

PR #5050 Review: DO NOT MERGE — Queue Diagnostics

Note: This is a DRAFT PR explicitly marked "DO NOT MERGE". This review treats it as a diagnostic/investigation branch.

---

Overview

This PR adds temporary DEBUG_QUEUE-prefixed instrumentation across the actor queue implementation to diagnose queue behavior. Changes span:

• rivetkit-rust/packages/rivetkit-core/src/actor/queue.rs — Rust-side warn-level trace points
• rivetkit-typescript/packages/rivetkit/src/registry/native.ts — TS-side debug logs around nextBatch
• rivetkit-typescript/packages/workflow-engine/src/context.ts — debug logs in executeQueueNextBatch

There is one incidental correctness fix: list_message_entries was refactored from a chained .await.context() return into a bound variable + explicit Ok(entries), which also makes the new log line possible.

---

Issues That Must Be Fixed Before Any Merge

1. Wrong log level in Rust (all tracing::warn! should be tracing::debug! or tracing::trace!)

All 7 Rust debug statements use tracing::warn!. This is the wrong level for diagnostic traces:

• warn is visible in all production deployments by default.
• It will fire on every enqueue_message, next_batch, try_receive_batch, and list_message_entries call, flooding operator logs.
• Per CLAUDE.md and project conventions, use tracing::debug! or tracing::trace! for diagnostic instrumentation.

The TypeScript side correctly uses .debug() and "debug" level — the Rust side should match.

2. DEBUG_QUEUE prefix in log messages

The DEBUG_QUEUE prefix signals temporary instrumentation. Remove before any permanent merge, or convert to proper structured fields (e.g., component = "queue").

---

Code Quality Notes

• has_preload variable (queue.rs:588): Clean addition. Clearer than re-calling .is_some() in the log.
• list_message_entries refactor (queue.rs:767-787): The extraction into a named variable is a valid improvement regardless of the debug logging. The original chained .await.context() was correct but opaque; the new form is easier to read and lets the compiler surface the type.
• TypeScript log style: Consistent with the existing logger().debug() and this.log("debug", ...) patterns. No issues.
• Structured fields: The Rust logs follow CLAUDE.md conventions (structured fields, lowercase messages, no string interpolation). Good.

---

Summary

Area	Status
Draft / DO NOT MERGE marker	Expected for diagnostic branch
Rust log level (warn instead of debug)	Must fix before merge
DEBUG_QUEUE prefixes in messages	Must remove before merge
TS log levels	Correct
Incidental list_message_entries refactor	Clean, keep it
Test coverage	N/A (diagnostic-only change)
Security / performance	No concerns beyond log spam from warn level

Bottom line: The diagnostic intent is clear and the instrumentation covers the right call sites. Before this could ever land (if the investigation yields a follow-up fix PR), downgrade all Rust tracing::warn! calls to tracing::debug! and strip the DEBUG_QUEUE prefixes.