jlcodes99/cockpit-tools · error
not_available
not_available
Error message
${skipped?.reason} || not_available What it means
Guard in CodexInstanceLaunchProgressModal.addAccountToApiService: appendCodexLocalAccessAccounts succeeded, but the target accountId is absent from result.syncedAccountIds — the backend skipped it. The skipped entry's reason is used as the error message, defaulting to 'not_available' when no reason is recorded, and the API-service addition is treated as failed.
Source
Thrown at src/components/CodexInstanceLaunchProgressModal.tsx:721
retryInstanceId: state.instanceId,
},
);
};
const addAccountToApiService = async () => {
if (!authFailure?.apiOnlyAvailable || !accountId || apiActionBusy) return;
setApiActionBusy(true);
setActionError(null);
try {
const result =
await codexLocalAccessService.appendCodexLocalAccessAccounts([
accountId,
]);
if (!result.syncedAccountIds.includes(accountId)) {
const skipped = result.skippedAccounts.find(
(item) => item.accountId === accountId,
);
throw new Error(skipped?.reason || "not_available");
}
setState(null);
window.dispatchEvent(
new CustomEvent("app-request-navigate", {
detail: "codex-api-service",
}),
);
} catch (error) {
setActionError(
t("codex.switchAuth.apiServiceAddFailed", {
error: String(error).replace(/^Error:\s*/, ""),
}),
);
} finally {
setApiActionBusy(false);
}
};
View on GitHub (pinned to 1ed8b77992)
Solutions
- Read the backend skip reason for the account (expired/invalid credentials, already synced, locked) and fix the underlying cause
- Re-run the API-service addition after repairing the account
- Surface the specific reason instead of the 'not_available' default when diagnosing
Defensive patterns
Strategy: fallback
When it happens
Trigger: Thrown at src/components/CodexInstanceLaunchProgressModal.tsx:721 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of jlcodes99/cockpit-tools@1ed8b77992 (2026-09-05).
Data as JSON: /api/errors/e49d6b9f382dc8a0.
Report an issue: GitHub.