durable-execution

Diagnose and stabilize Restate-backed durable workflow executions in Navigator.

Updated Aug 27, 2026

Search Tags:#durable execution #heartbeat #restate #cronjob #incident diagnosis #workflow reliability

Ready to run

npx skills add https://github.com/neon-law-foundation/navigator --skill durable-execution-neon-law-foundation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: durable-execution
Source: https://github.com/neon-law-foundation/navigator/tree/main/.claude/skills/durable-execution
Command: npx skills add https://github.com/neon-law-foundation/navigator --skill durable-execution-neon-law-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you keep Navigator's Restate-backed workflows alive, diagnose why scheduled or manual runs did not fire, and fix the issues that can silently interrupt binding legal operations.

Core Features & Use Cases

Workflow reliability: Maintains the submit and run split between workflows and workflows-service so durable execution stays predictable.
Incident diagnosis: Identifies common failure modes such as missing trigger images, registration drift, stale auth tokens, Forbid wedges, and email backend misconfiguration.
Operational guardrails: Reinforces the Heartbeat liveness canary, idempotency alignment, image copy requirements, and safe debugging practices that avoid exposing client content.

Quick Start

Ask me to investigate a missing workflow run, summarize the most likely failure mode, and give the safest fix path.

Frequently Asked Questions about durable-execution

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

FAQPage Schema

Why did my scheduled cronjob workflow fail to fire?▼

Scheduled cronjob workflows fail to fire due to missing trigger images, registration drift, or stale auth tokens. Diagnosing the missing run involves checking the Heartbeat liveness canary and verifying worker image integrity within the workflows-service stack to identify the specific failure mode.

How do I diagnose a wedged durable workflow execution?▼

Diagnosing a wedged durable workflow requires deterministic failure detection to identify Forbid wedges or email backend misconfiguration. You must check idempotency alignment and registration drift in the Restate-backed workflows-service stack to stabilize the interrupted execution.

What is durable execution for legal workflow reliability?▼

Durable execution maintains a predictable submit and run split between workflows and the workflows-service. It keeps Restate-backed binding legal operations alive by enforcing heartbeat monitoring and idempotency alignment, ensuring critical processes continue running reliably without silent interruptions.

Can I debug failed manual workflow runs without exposing confidential client data?▼

Debugging failed manual runs requires identifier-only debugging that protects client confidentiality. This operational guardrail enforces safe diagnostic practices within the workflows-service stack, allowing you to investigate failure modes and stabilize executions without exposing sensitive legal content.

How do I fix registration drift in Restate-backed workflows?▼

Fixing registration drift involves verifying worker image integrity and enforcing idempotency alignment within the Restate-backed workflows-service stack. Deterministic failure detection identifies the drift causing failed scheduled or manual runs, allowing you to restore predictable durable execution.

When do I need heartbeat monitoring for workflow reliability?▼

Heartbeat monitoring is needed to maintain liveness canaries for Restate-backed workflows. It detects silent interruptions in binding legal operations by enforcing operational guardrails, ensuring the submit and run split between workflows and workflows-service stays predictable and stable.