windmill-labs/windmill · error · Error

HTTP error: ${response.status}

Error message

HTTP error: ${response.status}

What it means

In frontend/src/lib/components/BedrockCredentialsCheck.svelte:33, checkApiCredentials fetches /api/w/<workspace>/ai/check_bedrock_credentials and throws "HTTP error: <status>" when the response is not ok. It signals the backend rejected the credentials check request rather than returning a JSON verdict.

Source

Thrown at frontend/src/lib/components/BedrockCredentialsCheck.svelte:33

	type CheckStatus = 'idle' | 'loading' | 'success' | 'error'

	let apiStatus: CheckStatus = $state('idle')
	let apiResult: CredentialsCheckResult | null = $state(null)

	let workerStatus: CheckStatus = $state('idle')
	let workerResult: (CredentialsCheckResult & { worker?: string }) | null = $state(null)

	let isChecking = $state(false)

	async function checkApiCredentials() {
		apiStatus = 'loading'
		apiResult = null

		try {
			const response = await fetch(`/api/w/${$workspaceStore}/ai/check_bedrock_credentials`)
			if (!response.ok) {
				throw new Error(`HTTP error: ${response.status}`)
			}
			apiResult = await response.json()
			apiStatus = apiResult?.available ? 'success' : 'error'
		} catch (err) {
			apiResult = {
				available: false,
				error: err instanceof Error ? err.message : 'Unknown error'
			}
			apiStatus = 'error'
		}
	}

	async function checkWorkerCredentials() {
		workerStatus = 'loading'
		workerResult = null

		try {
			// Create minimal flow with AI agent dry_run step

View on GitHub (pinned to e474e8803c)

Solutions

1. Verify the workspace has Bedrock/AWS credentials configured (instance or workspace settings)
2. Check network tab for the exact status and backend logs for the underlying cause
3. Confirm the deployment includes the AI/Bedrock endpoints
4. Re-login if the status is 401/403

null

null

try {
  const res = await fetch(url);
  if (!res.ok) throw new Error(`HTTP error: ${res.status}`);
  apiResult = await res.json();
} catch (err) {
  apiResult = { available: false };
  apiStatus = 'error';
  console.error('Bedrock credentials check failed:', err);
}

When it happens

Trigger: GET check_bedrock_credentials returns 4xx/5xx — e.g. workspace has no AWS/Bedrock configuration, the user lacks permission, or the endpoint is unavailable in this deployment/edition.

Common situations: Self-hosted instance without the Bedrock integration; expired workspace token (401/403); misconfigured AWS credentials on the server (500).

Understand the failure class

Background: "API error: {status}" and "HTTP 401/403/404/429/5xx" errors: non-2xx HTTP responses explained — this error's family across 27 libraries.

Related errors

• ApiError with mapped HTTP status message (e.g. "Not Found",
• Generic Error: status: ${errorStatus}; status text: ${errorS
• Couldn't fetch resource types from hub ${hubBaseUrl}: ${(awa
• Couldn't fetch resource types from public hub:
• GET assets/graph -> ${res.status}: ${await res.text()}

AI-assisted analysis of windmill-labs/windmill@e474e8803c (2026-09-03). Data as JSON: /api/errors/743a7d20aa606835. Report an issue: GitHub.