fix(rivetkit): use gatewayId instead of requestId in connection persistence log

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

Service	Status	Web	Updated (UTC)
website	❌ Build Failed (View Logs)	Web	Feb 24, 2026 at 4:00 am
ladle	❌ Build Failed (View Logs)	Web	Feb 24, 2026 at 4:00 am
mcp-hub	✅ Success (View Logs)	Web	Feb 24, 2026 at 3:59 am
frontend-cloud	❌ Build Failed (View Logs)	Web	Feb 24, 2026 at 3:59 am
frontend-inspector	❌ Build Failed (View Logs)	Web	Feb 24, 2026 at 3:59 am

[NathanFlurry]

• fix(rivetkit): harden sqlite-vfs lifecycle, remove getSqliteVfs #4277
• fix(sqlite-vfs): derive vfs types from Factory #4276
• fix(rivetkit): use gatewayId instead of requestId in connection persistence log #4275 👈 (View in Graphite)
• chore(rivetkit): fix sqlite-vfs for next-js & cf workers #4271 : 1 other dependent PR (#4272 )
• chore(rivetkit): fix run engine config #4268 : 1 other dependent PR (#4273 )
• chore: multiplayer cookbook patterns #4261 : 1 other dependent PR (#4266 )
• docs: document queue with interval pattern #4265
• chore(rivetkit): migrate to sqlite instance per-actor for concurrency optimizations #4264
• docs: workflows #4256
• chore(rivetkit): update conns to be hibernatable #4260
• chore(inspector): add back database tab #4255
• chore: impl canInvoke for matchmaker #4253
• chore: multiplayer cookbook #4200 : 1 other dependent PR (#4201 )
• feat(dashboard): bring new tabs back #4249
• fix(rivetkit): fix sqlite teardown logic #4259
• 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: fix(rivetkit): use gatewayId instead of requestId in connection persistence log

Status: LGTM - Simple, correct bug fix.

Summary

This is a one-line fix correcting a copy-paste error in the connection persistence log statement in state-manager.ts:464. The gatewayId field was accidentally being populated with hibernatableDataRaw.requestId instead of hibernatableDataRaw.gatewayId, causing the log to output the same value for both fields.

Assessment

Correctness: The fix is straightforwardly correct. Before the fix, the log entry had:

gatewayId: idToStr(hibernatableDataRaw.requestId)  // wrong - was using requestId
requestId: idToStr(hibernatableDataRaw.requestId)  // correct

After the fix, both fields reference their correct source properties.

No issues found:

• The change is minimal and targeted
• No logic is altered, only the log field source is corrected
• No security or performance implications
• Consistent with the existing structured logging pattern used throughout the codebase

This fix improves observability by ensuring the gatewayId field in persistence logs reflects the actual gateway ID rather than duplicating the request ID, which matters when debugging connection issues or tracing activity through logs.