paperclipai/paperclip · error · Error
Routine run ${run.id} did not create or coalesce an executio
Error message
Routine run ${run.id} did not create or coalesce an execution issue What it means
Invariant check after a routine run finishes: every run must produce (or coalesce into) a linked issue, but run.linkedIssueId is still null. Fires when issue creation was skipped, failed silently, or the run short-circuited before the issue step; the run lifecycle logic is at fault.
Source
Thrown at server/src/services/pipelines.ts:3011
variables,
},
variables,
descriptionAppendix: [
buildPipelineAutomationIssueTitlePrefix(detail),
buildPipelineStageEntryPreamble(detail),
buildPipelineCaseContextMarkdown({
...detail,
breakdownMechanics,
triggeringEventId: execution.triggeringEventId,
outputSummaries,
}),
].filter(Boolean).join("\n\n"),
});
if (!run.linkedIssueId) {
const failureReason = typeof run.failureReason === "string" && run.failureReason.trim().length > 0
? run.failureReason.trim()
: null;
throw new Error(
failureReason
? `Routine run ${run.id} failed: ${failureReason}`
: `Routine run ${run.id} did not create or coalesce an execution issue`,
);
}
const [updated] = await db
.update(pipelineAutomationExecutions)
.set({
status: "succeeded",
executionIssueId: run.linkedIssueId,
error: null,
updatedAt: nowDate(),
})
.where(eq(pipelineAutomationExecutions.id, execution.id))
.returning();
await db
.insert(pipelineCaseIssueLinks)
.values({View on GitHub (pinned to 120ae5428f)
Solutions
- Check routine execution configuration and logs to learn why no execution issue was created or coalesced, then retry.
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at server/src/services/pipelines.ts:3011 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/c92645f6db9502ef.
Report an issue: GitHub.