Add a retry action for partial publications, and surface real API errors

package.json

@@ -9,7 +9,8 @@
     "dev:clean": "vite --force",
     "build": "vite build",
     "preview": "vite preview",
-    "clean": "rm -rf node_modules/.vite && rm -rf dist"
+    "clean": "rm -rf node_modules/.vite && rm -rf dist",
+    "test": "vitest run"
   },
   "dependencies": {
     "@radix-ui/react-alert-dialog": "^1.1.15",
@@ -63,6 +64,7 @@
     "tailwindcss-scrollbar": "^0.1.0",
     "typescript": "^5.5.3",
     "typescript-eslint": "^8.3.0",
-    "vite": "^6.2.2"
+    "vite": "^6.2.2",
+    "vitest": "^4.1.10"
   }
 }

src/App.tsx

@@ -119,7 +119,8 @@ function App() {
     setEndDate: cronJobHistorySetEndDate,
     resetFilters: cronJobHistoryResetFilters,
     setPageSize: cronJobHistorySetPageSize,
-    setPage: cronJobHistorySetPage
+    setPage: cronJobHistorySetPage,
+    refresh: refreshCronJobHistory
   } = useCronJobHistory({ isCacheBust, setErrorWithScroll });
 
   const {
@@ -303,6 +304,7 @@ function App() {
                   cronJobHistoryTotalPages={cronJobHistoryTotalPages}
                   cronJobHistoryCurrentPage={cronJobHistoryCurrentPage}
                   cronJobHistorySetPage={cronJobHistorySetPage}
+                  cronJobHistoryOnRetryComplete={refreshCronJobHistory}
                   overviewTimeRange={overviewTimeRange}
                   setOverviewTimeRange={setOverviewTimeRange}
                   overviewHistoryData={overviewHistoryData}

src/api/index.ts

@@ -7,11 +7,35 @@ export interface CronJob {
   updated_at: string;
 }
 
+export interface MessageRunDetails {
+  url?: string;
+  sent?: string[];
+  failed?: string[];
+  manual?: boolean;
+}
+
 export interface CronJobHistory {
   name: string;
   timestamp: string;
   status: number;
   output?: string;
+  /** Only present on message runs recorded after the details column was added. */
+  details?: MessageRunDetails;
+}
+
+export interface RetryMessageOutcome {
+  api_name: string;
+  success: boolean;
+  error?: string;
+}
+
+export interface RetryMessageResult {
+  url: string;
+  status: number;
+  message: string;
+  succeeded?: string[] | null;
+  failed?: string[] | null;
+  outcomes?: RetryMessageOutcome[] | null;
 }
 
 export interface CronJobHistoryResponse {
@@ -143,6 +167,42 @@ export const updateCronSchedule = async (name: string, schedule: string): Promis
   }
 };
 
+/**
+ * Re-sends a repository to the integrations that missed it. Omitting `url` lets
+ * Content Maestro fall back to the most recently published repository, which is
+ * what a partial run has just consumed.
+ */
+export const retryMessagePost = async (
+  apis: string[],
+  url?: string
+): Promise<RetryMessageResult> => {
+  const settings = getApiSettings();
+
+  if (!isApiConfigured()) {
+    throw new Error("API not configured. Check the Content Maestro settings.");
+  }
+
+  const response = await fetch(`${settings.contentMaestro.apiBaseUrl}/api/message/retry`, {
+    method: "POST",
+    headers: {
+      "Content-Type": "application/json",
+      Authorization: `Bearer ${settings.contentMaestro.apiBearerToken}`,
+    },
+    body: JSON.stringify(url ? { apis, url } : { apis }),
+  });
+
+  if (!response.ok) {
+    if (response.status === 429) {
+      throw new Error("Rate limit exceeded. Please try again later.");
+    }
+    // Content Maestro answers errors as plain text.
+    const detail = (await response.text()).trim();
+    throw new Error(detail || `Failed to retry the publication: ${response.status}`);
+  }
+
+  return response.json();
+};
+
 export const updateCronStatus = async (name: string, is_active: boolean): Promise<void> => {
   const settings = getApiSettings();
   const isConfigured = isApiConfigured();