paperclipai/paperclip · error

Job not found: ${jobId}

Error message

Job not found: ${jobId}

What it means

triggerJob looked up the job by id in the plugin job store and found no record, meaning the jobId does not exist (or was deleted) at trigger time.

Source

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

        jobLog.error(
          { err: err instanceof Error ? err.message : String(err) },
          "failed to advance schedule pointer",
        );
      }
    }
  }

  // -----------------------------------------------------------------------
  // Core: manual trigger
  // -----------------------------------------------------------------------

  async function triggerJob(
    jobId: string,
    trigger: "manual" | "retry" = "manual",
  ): Promise<TriggerJobResult> {
    const job = await jobStore.getJobById(jobId);
    if (!job) {
      throw new Error(`Job not found: ${jobId}`);
    }

    if (job.status !== "active") {
      throw new Error(
        `Job "${job.jobKey}" is not active (status: ${job.status})`,
      );
    }

    // Overlap prevention
    if (activeJobs.has(jobId)) {
      throw new Error(
        `Job "${job.jobKey}" is already running — cannot trigger while in progress`,
      );
    }

    // Also check DB for running runs (defensive — covers multi-instance)
    const existingRuns = await db
      .select()

View on GitHub (pinned to 120ae5428f)

Solutions

1. Verify the job ID; list registered jobs for the plugin and use a valid jobId.

When it happens

Trigger: Thrown at server/src/services/plugin-job-scheduler.ts:445 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/a15bb0356f209fd1. Report an issue: GitHub.