FlowiseAI/Flowise · error · Error

HTTP Error ${res.status}: ${res.statusText}

Error message

HTTP Error ${res.status}: ${res.statusText}

What it means

Thrown by RequestsDelete tool's _call when secureFetch returns a response whose ok flag is false, i.e. an HTTP status outside the 2xx range. The message includes the numeric status and statusText (e.g. 'HTTP Error 404: Not Found'). This is the canonical 'the server rejected the DELETE' signal.

Source

Thrown at packages/components/nodes/tools/RequestsDelete/core.ts:176

                console.warn('Failed to process queryParamsSchema:', error)
            }
        } else if (params.queryParams && Object.keys(params.queryParams).length > 0) {
            // Fallback: treat all parameters as query parameters if no schema is defined
            const url = new URL(finalUrl)
            Object.entries(params.queryParams).forEach(([key, value]) => {
                url.searchParams.append(key, String(value))
            })
            finalUrl = url.toString()
        }

        try {
            const res = await secureFetch(finalUrl, {
                method: 'DELETE',
                headers: requestHeaders
            })

            if (!res.ok) {
                throw new Error(`HTTP Error ${res.status}: ${res.statusText}`)
            }

            const text = await res.text()
            return text.slice(0, this.maxOutputLength)
        } catch (error) {
            throw new Error(`Failed to make DELETE request: ${error instanceof Error ? error.message : 'Unknown error'}`)
        }
    }
}

View on GitHub (pinned to abe4a8601a)

Solutions

1. Check the status code: 401/403 -> fix auth headers; 404 -> verify the URL/resource exists; 405 -> confirm DELETE is supported; 5xx -> retry or contact the API provider.
2. Ensure required headers (Authorization, Content-Type, custom API keys) are set on the node.
3. Confirm the URL is correct and the resource has not already been deleted.
4. For transient 5xx/429, retry with backoff.

Example fix

// before: missing auth -> 401
await tool._call({})
// after
// (configure headers on the node or pass at construction)
const tool = new RequestsDelete({ name: 'del', url: 'https://api.example.com/x', headers: { Authorization: 'Bearer TOKEN' } })
await tool._call({})

function expectStatusOk(status: number): boolean {
  return status >= 200 && status < 300
}
// (this error originates server-side; pre-validation is limited to ensuring URL + headers)

null

try {
  await tool.call(arg)
} catch (e) {
  const m = e instanceof Error ? e.message : ''
  const match = m.match(/HTTP Error (\d+):/)
  if (match) {
    const status = Number(match[1])
    if (status === 401 || status === 403) { /* fix auth */ }
    else if (status === 404) { /* verify resource */ }
    else if (status >= 500) { /* retry/backoff */ }
  } else throw e
}

When it happens

Trigger: Target resource does not exist (404); missing/invalid auth credentials (401/403); the resource is already deleted (410); rate limited (429); server error (5xx); wrong URL/method not allowed by the server (405); trying to delete a resource the API does not allow.

Common situations: Expired or missing auth token; URL points to a resource already removed; the endpoint expects a different HTTP method; CORS/server policy rejects the request; transient 5xx outage.

Related errors

• Microsoft Graph API error: ${response.status} ${response.sta
• HTTP Error ${res.status}: ${res.statusText}
• HTTP Error ${res.status}: ${res.statusText}
• HTTP Error ${res.status}: ${res.statusText}
• ${errorMessage}

AI-assisted analysis of FlowiseAI/Flowise@abe4a8601a (2026-08-12). Data as JSON: /api/errors/c0b59643a9fb7c38. Report an issue: GitHub.