paperclipai/paperclip · error
scope.detail
Error message
scope.detail
What it means
resolveTaskWatchdogMutationScope returned kind 'invalid' for the actor's run, and scope.detail (the scope resolver's reason, e.g. missing or malformed watchdog binding) is surfaced verbatim as the 403 error.
Source
Thrown at server/src/routes/issues.ts:4768
message: "Suggested-task creation requires independent authorization for every selected task",
});
}
}
return true;
}
async function resolvePendingReviewInteractionRestriction(
issue: {
id: string;
companyId: string;
status: string;
reviewPolicy?: IssueReviewPolicy | null;
createdByAgentId?: string | null;
createdByUserId?: string | null;
},
interaction: {
id: string;
kind: string;
status: string;
createdByAgentId?: string | null;
createdByUserId?: string | null;
},
): Promise<{
restriction: IssueThreadInteractionCanonicalResolverPolicy | IssueThreadInteractionResolverRestriction;
binding: "explicit" | "legacy";
} | null> {
if (
issue.status !== "in_review"
|| interaction.status !== "pending"
|| (
interaction.kind !== "request_confirmation"
&& interaction.kind !== "request_checkbox_confirmation"
)
) return null;
if (!(await isIssueReviewVerdictInteraction(db, { issue, interaction }))) return null;
const requester = await resolveIssueReviewRequester(db, issue);View on GitHub (pinned to 01ad858492)
Solutions
- Correct the request so it satisfies the condition stated in the error message, then retry; see the throwing line in the named file for the exact check.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at server/src/routes/issues.ts:4604 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/084f179330f13fdd.
Report an issue: GitHub.