paperclipai/paperclip · error · AutoApprovalIssueMissingError
Issue not found
Error message
Issue not found
What it means
Not-found sentinel on the issues routes: the requested issue id does not exist (or is not visible in the caller's company scope), surfaced as an HttpError 404. Callers such as the CLI access-parity tests rely on this exact message to distinguish 'missing issue' from other failures.
Source
Thrown at server/src/routes/issues.ts:13097
await questionResponseDeliveries.deliver(interaction.id).catch((err) => {
logger.warn({
err,
companyId: issue.companyId,
issueId: issue.id,
interactionId: interaction.id,
}, "synchronous question response delivery failed; durable outbox will retry");
});
res.json(interaction);
},
);
router.post(
"/issues/:id/interactions/:interactionId/verdicts",
validate(submitIssueThreadInteractionVerdictsSchema),
async (req, res) => {
const id = req.params.id as string;
const interactionId = req.params.interactionId as string;
const issue = await getAccessibleResource(req, res, svc.getById(id), "Issue not found");
if (!issue) return;
const authorizedResolution = await getIssueThreadInteractionResolutionAuthorization(
req,
res,
issue,
interactionId,
);
if (!authorizedResolution) return;
const { interactionSvc, resolutionAuthorization } = authorizedResolution;
const actor = getActorInfo(req);
const { interaction, newlyResolvedItemIds } = await interactionSvc.submitItemVerdicts(
issue,
interactionId,
req.body,
{View on GitHub (pinned to 01ad858492)
Solutions
- Verify the issue id exists in the selected company.
- Check that the caller has access to the company containing the issue.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at server/src/routes/issues.ts:12079 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of paperclipai/paperclip@01ad858492 (2026-08-18).
Data as JSON: /api/errors/80abe4e3ae85fd42.
Report an issue: GitHub.