resonate-basic-debugging-typescript

Diagnose runtime and deployment issues in Resonate TypeScript applications.

6|Updated Jan 8, 2026

Search Tags:#typescript #debugging #troubleshooting #observability #rpc #determinism #resonate

Ready to run

npx skills add https://github.com/resonatehq/resonate-skills --skill resonate-basic-debugging-typescript

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resonate-basic-debugging-typescript
Source: https://github.com/resonatehq/resonate-skills/tree/main/resonate-basic-debugging-typescript
Command: npx skills add https://github.com/resonatehq/resonate-skills --skill resonate-basic-debugging-typescript

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help engineers identify and resolve runtime, deployment, and determinism issues affecting Resonate TypeScript workflows by guiding focused triage steps and observability checks so debugging is faster and more reproducible.

Core Features & Use Cases

Triage Flow & Checklist: Classify failures, confirm worker connectivity, inspect promise state and call graphs, and validate registration and serialization.
CLI & Observability Guidance: Which resonate CLI commands to run for starting a dev server, invoking workflows, inspecting trees and promises, and resolving external promises.
Determinism & Routing Checks: Concrete recommendations for avoiding non-deterministic APIs, correct yield* usage, and ensuring correct group routing for RPCs and workers.

Quick Start

Start a local Resonate server, run a minimal TypeScript worker, and invoke the failing promise to inspect its call graph and promise state.

Frequently Asked Questions about resonate-basic-debugging-typescript

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug stuck workflows and failed RPCs in TypeScript applications?▼

To debug stuck TypeScript workflows and failed RPCs, start a local Resonate server, run a minimal worker, invoke the failing promise, and inspect its call graph and promise state using the resonate CLI to isolate the failure.

What causes determinism errors in TypeScript SDK workers and how do I fix them?▼

Determinism errors in TypeScript SDK workers usually stem from non-deterministic APIs. Resolve them by following a determinism checklist that validates correct yield* usage and eliminates non-deterministic code from your workflow functions.

How do I inspect promise state and call graphs for Resonate TypeScript routing issues?▼

You inspect promise state and call graphs for Resonate TypeScript routing issues by running specific resonate CLI commands to view promise trees, validate worker registrations, and confirm correct group routing for RPCs.

Why are my Resonate TypeScript client RPC interactions failing during deployment?▼

Client RPC interactions fail during deployment when group routing or worker registration is misconfigured. Validate your routing configuration, confirm worker connectivity, and check the serialization checklist to ensure proper deployment.

What CLI commands do I need to troubleshoot Resonate TypeScript promise routing?▼

Troubleshooting Resonate TypeScript promise routing requires CLI commands to start a dev server, invoke workflows, inspect call trees, check promise states, and resolve external promises to pinpoint exact routing failures.

How do I validate serialization and registration when debugging Resonate TypeScript workers?▼

Validate serialization and registration when debugging Resonate TypeScript workers by applying a serialization checklist, confirming worker connectivity, and verifying that all functions are correctly registered with the server.