resonate-basic-debugging-python

A troubleshooting guide for Resonate applications written in Python. Resonate is a system that runs workflows durably, so they can resume after failures.

In plain words
What is it for?
Use it to investigate stuck workflows, repeated or unexpected retries, registration errors, async/await mistakes, server connection problems, and non-deterministic replays.
Why use it?
It helps identify whether a problem comes from Python code, the Resonate SDK, the server, worker setup, or workflow replay.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/resonatehq/resonate-skills/resonate-basic-debugging-python
Any agent
npx skills add resonatehq/resonate-skills --skill resonate-basic-debugging-python
Clone the repo
git clone --depth 1 https://github.com/resonatehq/resonate-skills

Made for: Claude Code, Codex.

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,388 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00062 $0.02388
Opus 5 $0.00031 $0.01194
Sonnet 5 $0.00012 $0.00478
Haiku 4.5 $0.00006 $0.00239

Measured 2d ago against content hash e1f2480f6b24, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

resonate-basic-debugging-python scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

resonate-basic-debugging-python/SKILL.md · 258 lines

How it starts

The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Resonate Debug and Troubleshoot — Python

Overview

Use this skill to diagnose Resonate runtime issues in Python. The Python SDK v0.7.0 uses async def + await (not generators); failure modes differ from TypeScript's generator-based v1 API and from the legacy v0.6.x Python SDK. Focus on reproducible symptoms, promise state, registration, and determinism.

For the language-agnostic replay + recovery mental model, read durable-execution first.

Triage flow

  1. Classify the failure: import/syntax error, runtime SDK error, server error code, workflow stuck/hanging, or unexpected replay behavior.
  2. Confirm Python is ≥ 3.12 and resonate-sdk>=0.7.0 is installed.
  3. Confirm the Resonate server is reachable: resonate dev starts it on localhost:8001 (Rust v0.9.x, single port — no separate store port).
  4. Confirm the worker process is running, connected to the right URL and group, and registered for the right functions.
  5. Inspect the promise state and call graph for the invocation ID.
  6. Validate determinism — no time.time(), no random.random(), no un-checkpointed side effects in the orchestrator body.

Version + compat pins

  • Python ≥ 3.12 — the SDK uses recent typing syntax. 3.11 and below won't import.
  • resonate-sdk>=0.7.0 — async/await rewrite; incompatible with v0.6.x API.
  • Resonate server v0.9.x (Rust, single port 8001) — run with resonate dev for local development.
  • resonate-sdk on PyPI (not resonate — the bare name is a different package).

If from resonate.resonate import Resonate fails, you either have the wrong package installed or you're on Python < 3.12.

Async/await pitfalls (Python-specific)

These are the most common Python-only footguns with the v0.7.0 SDK.

Forgot await before a Context call

async def foo(ctx: Context, arg: str) -> str:
    ctx.run(bar, arg)   # missing await; returns a future the SDK sees but you lose the result
    return "done"

The future is tracked by structured concurrency (the runtime will still join it before settling foo), but the result is lost and your orchestrator continues without it. Fix:

Read the full file on GitHub · 258 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 258 lines · 62 tokens per session scan A e1f2480f6b24

Subscribe to this mod's changes

resonate-basic-debugging-python is a skill published in the GitHub repository resonatehq/resonate-skills (6 stars, last pushed 10d ago), licensed Apache-2.0. It adds 62 tokens to every session and 2,388 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.