feat(frontend): ping actor if its in the crash loop

[jog1t]

Description

Added support for crash-loop actor status in the guard connectable inspector. This change introduces a new CrashLoopActor component that displays an error state with an exclamation triangle icon, informative messaging about retry behavior, and a "Ping Actor now" button when the actor is not scheduled for future retry. The component fetches additional status information and provides manual intervention capabilities for actors stuck in crash loops.

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

Service	Status	Web	Updated (UTC)
frontend-cloud	😴 Sleeping (View Logs)	Web	Mar 17, 2026 at 9:37 pm
frontend-inspector	😴 Sleeping (View Logs)	Web	Mar 17, 2026 at 9:34 pm
mcp-hub	✅ Success (View Logs)	Web	Mar 17, 2026 at 9:28 pm
website	❌ Build Failed (View Logs)	Web	Mar 17, 2026 at 9:28 pm
ladle	❌ Build Failed (View Logs)	Web	Mar 17, 2026 at 9:27 pm

[jog1t]

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(frontend): remove flashing upgrade notice #4451
• fix(frotnend): fix icons kiling the bundle #4450
• feat(frontend): ping actor if its in the crash loop #4448 👈 (View in Graphite)
• fix(engine): use proper paths for settings #4447
• feat(frontend): add outdated indicator to runners #4446
• main

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

[claude]

Updated review (previous feedback partially addressed)

Addressed since last review

• Button label changed from "Ping Actor now" to "Wake up Actor", consistent with the sleeping-actor button
• Wake button added to the crashed branch in UnavailableInfo

---

Remaining issues

1. Redundant query for rescheduleTs

CrashLoopActor issues its own useQuery call for actorStatusAdditionalInfoQueryOptions (with refetchInterval: 5_000) and then renders <QueriedActorStatusAdditionalInfo /> which issues the same query again. TanStack Query deduplicates the network request, but the refetchInterval option is set on only one of the observers, so the polling behaviour of the two observers can diverge. A simpler approach is to remove the outer useQuery and instead expose rescheduleTs from inside a shared hook or derive it from the same query result that QueriedActorStatusAdditionalInfo already fetches.

2. Button hidden without explanation when retry is already scheduled

When rescheduleInFuture is true, the wake button is omitted entirely. A user who lands on this screen while a retry is pending has no visual indication that the actor will retry automatically and no way to understand why the action is absent. Consider rendering a disabled button (or an inline note like "Retry scheduled in X") so the user has context. QueriedActorStatusAdditionalInfo already shows the retry time, so the message can be brief.

3. Missing crash error in CrashLoopActor

The crashed branch in UnavailableInfo renders <QueriedActorError /> to help the user understand why the actor failed. CrashLoopActor only renders <QueriedActorStatusAdditionalInfo />, which shows the next retry time but not the crash error. Adding <QueriedActorError actorId={actorId} /> would give users the same diagnostic information for crash-loop actors as they get for plain-crashed actors.

---

Minor

• PR description checklist is still entirely unchecked (test plan, self-review items).
• No automated tests for the new crash-loop UI branch.

[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
• example-elysia
• 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-kitchen-sink
• example-kitchen-sink-vercel
• multi-region-vercel
• multiplayer-game
• example-multiplayer-game-patterns
• example-multiplayer-game-patterns-vercel
• 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
• state
• state-vercel
• example-stream
• example-stream-vercel
• example-trpc

@rivetkit/cloudflare-workers

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

@rivetkit/framework-base

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

@rivetkit/next-js

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

@rivetkit/react

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

rivetkit

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

@rivetkit/sql-loader

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

@rivetkit/sqlite-vfs

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

@rivetkit/traces

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

@rivetkit/workflow-engine

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

@rivetkit/virtual-websocket

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

@rivetkit/engine-runner

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

@rivetkit/engine-runner-protocol

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

commit: 0638a17

[MasterPtato]

Change "ping actor now" to "wake" (same as when its sleeping)

Also change .with("crashed" branch to have a wake button as well