conductor-oss/conductor · error · Error

Failed to generate keys

Error message

Failed to generate keys

What it means

Error "Failed to generate keys" thrown in conductor-oss/conductor.

Source

Thrown at ui-next/src/shared/createAndDisplayApplication/state/services.ts:135

  } catch (error: any) {
    const errorMessage = await getErrorMessage(error);
    throw new Error(errorMessage ?? "Failed to create application");
  }
};

export const generateKeys = async (
  context: CreateAndDisplayApplicationMachineContext,
) => {
  const { authHeaders, applicationId } = context;
  const path = `/applications/${applicationId}/accessKeys`;
  try {
    return await fetchWithContext(
      path,
      {},
      { method: "POST", headers: { ...authHeaders } },
    );
  } catch {
    throw new Error("Failed to generate keys");
  }
};

View on GitHub (pinned to cf7c3e4a8a)

Solutions

1. Confirm the applicationId exists and the POST to /applications/{id}/accessKeys is authorized.
2. Check server logs; key generation fails server-side when the application is missing or the caller lacks access.
3. Retry the request after verifying network and authentication.

When it happens

Trigger: Thrown at ui-next/src/shared/createAndDisplayApplication/state/services.ts:135 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of conductor-oss/conductor@cf7c3e4a8a (2026-08-14). Data as JSON: /api/errors/bff0391c1fd8ecce. Report an issue: GitHub.