paperclipai/paperclip · error
Invalid extract search query
Error message
Invalid extract search query
What it means
400 from the extract search route: companySearchExtractQuerySchema failed to parse the query string; the schema's own first issue message is used, falling back to this generic text.
Source
Thrown at server/src/routes/issues.ts:5860
}
: {}),
updatedAt: now,
})
.where(and(
eq(issueRows.id, input.issue.id),
locked.queueRun && remainingIds.length === 0
? eq(issueRows.executionRunId, locked.queueRun.id)
: undefined,
));
return {
deleted,
queue: await buildQueuedCommentQueue({
executor: tx,
issue: input.issue,
activeRun: locked.activeRun,
actor: input.actor,
queueState: nextQueueState,
}),
};
});
}
function operatorInterruptCancelOptions(input: { issueId: string; actor: ReturnType<typeof getActorInfo> }) {
return {
errorCode: "operator_interrupted",
resultJson: {
operatorInterrupted: true,
interruptionSource: "issue_comment_interrupt",
interruptedIssueId: input.issueId,
interruptedByActorType: input.actor.actorType,
interruptedByActorId: input.actor.actorId,
},
eventMessage: "run interrupted by board comment",
eventPayload: {
issueId: input.issueId,View on GitHub (pinned to 5716fe907e)
Solutions
- Fix the offending parameter to satisfy the constraint stated in the error message (type, range, or allowed values), then retry.
- Refer to the route's request validation in the named file and the shared validators for the accepted format.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at server/src/routes/issues.ts:5713 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of paperclipai/paperclip@5716fe907e (2026-08-18).
Data as JSON: /api/errors/8d6985ef7c2f884b.
Report an issue: GitHub.