No resumable run found for workflow '${workflowName}' at pat

Error message

No resumable run found for workflow '${workflowName}' at path '${cwd}'.

What it means

The CLI could not find any resumable run for the given workflow name in the current directory when --resume was requested. The continuation lookup completed without error, but no matching run row exists, so the pre-flight throws buildNoResumableRunError(workflowName, cwd) instead of forking a child that would silently have nothing to resume. Message: 'No resumable run found for workflow <name> at path <cwd>.'

Source

Thrown at packages/cli/src/commands/workflow.ts:2080

        supersededRunId = await resolveRunIdArg(
          options.supersedesRunId,
          cwd,
          false,
          detachCodebase.id
        );
        await resolveSupersededRun(supersededRunId);
      }
    }

    // The run id the ack hands back. A continuation already has one; a fresh launch
    // gets a row written below, before the fork.
    let detachedRunId: string;
    // Only a row THIS process created may be failed when the child never takes it.
    // A continuation's row belongs to its own run.
    let launchedRunId: string | undefined;
    if (isContinuation) {
      if (resumeLookupError) throw buildResumeLookupFailureError(resumeLookupError);
      if (!continuationRun) throw buildNoResumableRunError(workflowName, cwd);
      detachedRunId = continuationRun.id;
    } else {
      // `Started` must mean a queryable run, so the row is written before the fork and
      // the child executes it rather than creating its own. Modeled on the
      // orchestrator's pre-created row (dispatchBackgroundWorkflowOwned), including
      // the stamps the executor only writes when IT creates the row. `working_path` is
      // the one field this process cannot know — the child cuts the worktree — so it
      // stays null until the child fills it in (write-once in the store).
      let detachedConversation;
      try {
        detachedConversation = await conversationDb.getOrCreateConversation(
          'cli',
          childConversationId
        );
      } catch (error) {
        const err = error as Error;
        throw new Error(
          `Failed to access database: ${err.message}\nHint: Check that DATABASE_URL is set and the database is running.`

View on GitHub (pinned to 0773b97458)

Solutions

Run from the same project path where the original run was launched
Confirm the exact workflow name as registered/discovered
Check the runs list (CLI/UI) to see whether a resumable run exists for that project
If no run exists, launch a fresh run without --resume

Example fix

// before
pnpm archon workflow run fix-issue --resume   # wrong cwd
// after
cd /path/to/original/checkout
pnpm archon workflow run fix-issue --resume

Defensive patterns

Strategy: validation

Validate before calling

// before `run --resume`, confirm a resumable run exists for this workflow+cwd
const runs = await listRuns({ workflow: name, cwd: process.cwd(), resumableOnly: true });
if (runs.length === 0) throw new Error(`No resumable run for '${name}' at ${process.cwd()}`);

Try / catch

try {
  await runWorkflow(name, { resume: true });
} catch (e) {
  if (String(e.message).startsWith('No resumable run found')) {
    // fall back to a fresh launch or correct the cwd/workflow name
  } else throw e;
}

Prevention

Resume from the same directory the original run was started in
Verify the workflow name matches the registered/discovered name
Check run state in the UI/CLI first; completed runs are not resumable
Script a runs lookup before any automated --resume call

When it happens

Trigger: Running `archon workflow run <name> --resume` (or with --detach) from a directory or for a workflow name that has no prior failed/interrupted run row matching both the workflow and the project path — the isContinuation / resume branch where continuationRun is undefined.

Common situations: Running --resume from a different checkout path than the original run; misspelling the workflow name; the previous run already completed or was resumed once (no longer resumable); the database was wiped or points at a different environment.

Related errors

AI-assisted analysis of coleam00/Archon@0773b97458 (2026-09-01). Data as JSON: /api/errors/a9172de209f5d054. Report an issue: GitHub.