paperclipai/paperclip · error

Worker for plugin "${job.pluginId}" is not running — cannot

Error message

Worker for plugin "${job.pluginId}" is not running — cannot trigger job

What it means

Dependency guard in triggerJob: workerManager.isRunning reports the plugin's worker process is not up, so the job could not actually execute. Start/restart the plugin worker before triggering; the stopped worker is at fault.

Source

Thrown at server/src/services/plugin-job-scheduler.ts:480

    const existingRuns = await db
      .select()
      .from(pluginJobRuns)
      .where(
        and(
          eq(pluginJobRuns.jobId, jobId),
          eq(pluginJobRuns.status, "running"),
        ),
      );

    if (existingRuns.length > 0) {
      throw new Error(
        `Job "${job.jobKey}" already has a running execution — cannot trigger while in progress`,
      );
    }

    // Check worker availability
    if (!workerManager.isRunning(job.pluginId)) {
      throw new Error(
        `Worker for plugin "${job.pluginId}" is not running — cannot trigger job`,
      );
    }

    // Create the run and dispatch (non-blocking)
    const run = await jobStore.createRun({
      jobId,
      pluginId: job.pluginId,
      trigger,
    });

    // Dispatch in background — don't block the caller
    void dispatchManualRun(job, run.id, trigger);

    return { runId: run.id, jobId };
  }

  /**

View on GitHub (pinned to 120ae5428f)

Solutions

1. Start the plugin's worker (load/activate the plugin) before triggering its jobs; check worker status in the plugin manager.

When it happens

Trigger: Thrown at server/src/services/plugin-job-scheduler.ts:480 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of paperclipai/paperclip@120ae5428f (2026-08-18). Data as JSON: /api/errors/2566d2287d20f9f7. Report an issue: GitHub.