mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-11-12 22:56:58 +01:00
## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work > - When a task's run fails, the board recovers it with a Retry button, so that button must either start work or say why it did not > - An audit of every Retry-type button found three gaps. The task Retry shown during a scheduled retry's countdown returned "accepted" but changed nothing. A stale Retry looked like success in the Inbox. "Retry now" skipped the task's read and change checks, so a member who cannot see a private task could start its retry > - This pull request makes the task Retry start a scheduled retry immediately, makes every Retry that did not start work say why, and gives "Retry now" the same authorization as the task Retry > - The benefit is that no Retry click silently does nothing ## Linked Issues or Issue Description Refs #19831. The board reported a dead Retry button. A read-only audit of every Retry button confirmed: - **Task Retry during a scheduled retry was a no-op.** `TaskInterruptionPresentation.canRetry` is true in `retry_scheduled`, so `ExecutionBlockerNotice` shows Retry. `requestTaskRetry` treats `scheduled_retry` as busy and inserts a `coalesced` wake pointing at that run. `resumeTaskRetry` reads only `deferred_issue_execution`, and dispatch uses coalesced user wakes only to carry comments. Nothing promoted the run: the API answered 202 `accepted: true` and the countdown did not change. - **A stale Retry looked like success.** `accepted: false, stale: true` comes back as HTTP 200. The Inbox ignored `accepted` and opened the task as if work had started. The task page showed no reason. - **"Retry now" checked less than the task Retry.** It ran only `assertBoard` and `getAccessibleResource`, skipping `assertIssueReadAllowed` and `issue:mutate`. A company member who cannot read a private task could promote that task's scheduled retry. - **"Retry now" said nothing for some outcomes.** It toasted only `promoted` and `gate_suppressed`. ## What Changed - `server/src/services/task-retry.ts`: when the Retry coalesces into the task's latest run and that run is `scheduled_retry` (with no other Retry already active), the receipt returns `scheduledRetryRunId`. - `server/src/routes/issues.ts`: - `POST /issues/:id/retry` then promotes that run through the existing `retryScheduledRetryNow`, the same path "Retry now" uses. It logs `issue.scheduled_retry_retry_now` with `source: "task_retry"` and returns `scheduledRetry: { outcome, message }`. - `POST /issues/:id/scheduled-retry/retry-now` now runs `assertIssueReadAllowed` and `decideIssueAccess("issue:mutate")`, matching `/retry`. A private task the member cannot read now answers 404. - `ui/src/hooks/useTaskRetry.ts`: new `taskRetryNotStartedReason`. When a Retry did not start work (stale, or a scheduled retry that is gate-suppressed, waiting, or gone), the hook returns that reason as its error. `ExecutionBlockerNotice` and `StalledDependencyNotice` already display it. - `ui/src/pages/Inbox.tsx`: a task Retry that did not start work shows the reason in the error toast and does not navigate. - `ui/src/hooks/useRetryNowMutation.ts` and `IssueScheduledRetryCard.tsx`: every "Retry now" outcome now shows its headline and message, including `no_scheduled_retry` on the card. - `ui/src/api/issues.ts`: `retryTask`'s response type includes `scheduledRetry`. ## Verification Red/green (each new test fails against master and passes with this PR): - `server/src/__tests__/issue-scheduled-retry-routes.test.ts`: - "starts a scheduled retry now when the task Retry is clicked during its countdown": 202 with `scheduledRetry.outcome: "promoted"`, the same run becomes `queued`, and no second retry run is created. - "refuses Retry now on a private task the member cannot see, like the task Retry": on master "Retry now" answers 200 `promoted`; now both routes answer 404 and the run stays `scheduled_retry`. - The seed now adds the board user's membership, which the stricter route needs. All 33 tests pass. - `ui/src/hooks/useTaskRetry.test.tsx`: a replaced attempt, a gate-held scheduled retry and a waiting scheduled retry each show their reason; a promoted one shows nothing extra. - `ui/src/pages/Inbox.test.tsx`: an Inbox Retry that did not start work (stale, or gate-held) toasts the reason and does not navigate. - `ui/src/components/IssueScheduledRetryCard.test.tsx`: "explains when there was no scheduled retry left to start". Other Retry buttons: the chat failed-run Retry already reports stopped and failed retries (`agents.test.ts`). Agent lifecycle "Retry now" and cost "Retry accounting" start no task work and already surface their API errors. Regression and static checks: - UI: 7 files, 168 passed. Server: task-retry and scheduled-retry suites, 149 passed. `issue-agent-mutation-ownership-routes.test.ts` passed. - `maintenance-server-routes.test.ts` "assembled maintenance server production wiring" fails identically on master on this Mac (`ensure-build-deps`). - `tsc --noEmit` passes for `server` and `ui/src`. `pnpm check:token-gates` is clean. ## Risks - A task Retry during a scheduled retry now starts the run immediately, through the existing "Retry now" promotion gates (pause, budget, cleanup waits). A gate that holds it is reported, not bypassed. - "Retry now" is stricter: a member without read or change access to the task gets 404 or 403, as on `/retry`. - No schema change. ## Model Used - Claude Opus 5.5 (`claude-opus-5-5`), Anthropic, via Claude Code with tool use (shell, file edits). ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [x] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work - [x] I have searched GitHub for duplicate or related PRs and linked them above - [x] I have either (a) linked existing issues with `Fixes: #` / `Closes #` / `Refs #` OR (b) described the issue in-PR following the relevant issue template - [x] I have not referenced internal/instance-local Paperclip issues or links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip` URLs) - [x] My branch name describes the change (e.g. `docs/...`, `fix/...`) and contains no internal Paperclip ticket id or instance-derived details - [x] I have run tests locally and they pass - [x] I have added or updated tests where applicable - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [ ] All Paperclip CI gates are green - [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups - [x] I will address all Greptile and reviewer comments before requesting merge 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
99 lines
3.3 KiB
TypeScript
99 lines
3.3 KiB
TypeScript
import { useCallback } from "react";
|
|
import { useMutation, useQueryClient, type UseMutationResult } from "@tanstack/react-query";
|
|
import type { IssueRetryNowOutcome, IssueRetryNowResponse } from "@paperclipai/shared";
|
|
import { ApiError } from "../api/client";
|
|
import { issuesApi } from "../api/issues";
|
|
import { useToastActions } from "../context/ToastContext";
|
|
import { queryKeys } from "../lib/queryKeys";
|
|
|
|
export type RetryNowError = {
|
|
message: string;
|
|
outcomeMessage: string | null;
|
|
status: number | null;
|
|
};
|
|
|
|
function readErrorMessage(error: unknown): string {
|
|
if (error instanceof ApiError) {
|
|
if (typeof error.message === "string" && error.message.trim().length > 0) return error.message;
|
|
return `Request failed (${error.status})`;
|
|
}
|
|
if (error instanceof Error && error.message) return error.message;
|
|
return "The request failed. Try again in a moment.";
|
|
}
|
|
|
|
export const RETRY_NOW_OUTCOME_HEADLINE: Record<IssueRetryNowOutcome, string> = {
|
|
promoted: "Retry promoted",
|
|
already_promoted: "Retry already running",
|
|
waiting: "Retry waiting",
|
|
no_scheduled_retry: "No scheduled retry",
|
|
gate_suppressed: "Couldn't retry now",
|
|
};
|
|
|
|
export function useRetryNowMutation(
|
|
issueId: string | null | undefined,
|
|
): UseMutationResult<IssueRetryNowResponse, unknown, void, unknown> & {
|
|
lastError: RetryNowError | null;
|
|
} {
|
|
const queryClient = useQueryClient();
|
|
const { pushToast } = useToastActions();
|
|
|
|
const mutation = useMutation({
|
|
mutationFn: () => {
|
|
if (!issueId) throw new Error("Missing issue id");
|
|
return issuesApi.retryScheduledRetryNow(issueId);
|
|
},
|
|
onSuccess: (response) => {
|
|
if (issueId) {
|
|
queryClient.invalidateQueries({ queryKey: queryKeys.issues.detail(issueId) });
|
|
queryClient.invalidateQueries({ queryKey: queryKeys.issues.activity(issueId) });
|
|
queryClient.invalidateQueries({ queryKey: queryKeys.issues.runs(issueId) });
|
|
queryClient.invalidateQueries({ queryKey: queryKeys.issues.liveRuns(issueId) });
|
|
queryClient.invalidateQueries({ queryKey: queryKeys.issues.activeRun(issueId) });
|
|
}
|
|
pushToast({
|
|
title: RETRY_NOW_OUTCOME_HEADLINE[response.outcome],
|
|
body: response.message,
|
|
tone: response.outcome === "promoted" || response.outcome === "already_promoted" ? "success"
|
|
: response.outcome === "gate_suppressed" ? "error" : "info",
|
|
});
|
|
},
|
|
onError: (error) => {
|
|
pushToast({
|
|
title: "Couldn't retry now",
|
|
body: readErrorMessage(error),
|
|
tone: "error",
|
|
});
|
|
},
|
|
});
|
|
|
|
const reset = mutation.reset;
|
|
const wrappedReset = useCallback(() => reset(), [reset]);
|
|
|
|
const lastError: RetryNowError | null = (() => {
|
|
if (mutation.error) {
|
|
const apiError = mutation.error instanceof ApiError ? mutation.error : null;
|
|
return {
|
|
message: readErrorMessage(mutation.error),
|
|
outcomeMessage: null,
|
|
status: apiError?.status ?? null,
|
|
};
|
|
}
|
|
if (mutation.data && mutation.data.outcome === "gate_suppressed") {
|
|
return {
|
|
message: mutation.data.message,
|
|
outcomeMessage: mutation.data.message,
|
|
status: null,
|
|
};
|
|
}
|
|
return null;
|
|
})();
|
|
|
|
return {
|
|
...mutation,
|
|
reset: wrappedReset,
|
|
lastError,
|
|
} as UseMutationResult<IssueRetryNowResponse, unknown, void, unknown> & {
|
|
lastError: RetryNowError | null;
|
|
};
|
|
}
|