langflow-ai/langflow · error · HTTPException
The {provider_label} integration is not configured for {oper
Error message
The {provider_label} integration is not configured for {operation}. What it means
500 from BaseDeploymentMapper.parse_adapter_slot: the code asked to parse a provider-internal payload, but the PayloadSlot for that boundary is None — the provider integration never registered/configured that slot. This is explicitly an internal error ('the user cannot fix it'): the slot_name is logged server-side but withheld from the client. Indicates a deployment-provider integration that is half-configured or a code path hitting an unimplemented slot.
Source
Thrown at src/backend/base/langflow/api/v1/mappers/deployments/base.py:936
self,
*,
slot: PayloadSlot[Any] | None,
slot_name: str,
raw: Any,
operation: str = "this operation",
) -> Any:
"""Parse a non-user-supplied adapter-boundary payload, raising 500 on failure.
Use for adapter/provider results and mapper-built payloads headed to the adapter.
Failures are internal errors — the user cannot fix them.
``slot_name`` is logged for debugging but not exposed to the user.
See ``parse_api_request_slot`` for user-supplied input.
"""
provider_label = self.get_provider_label()
if slot is None:
logger.error("Payload slot '%s' is not configured for %s", slot_name, provider_label)
msg = f"The {provider_label} integration is not configured for {operation}."
raise HTTPException(status_code=status.HTTP_500_INTERNAL_SERVER_ERROR, detail=msg)
try:
return slot.parse(raw)
except AdapterPayloadMissingError as exc:
logger.error("Empty adapter payload for slot '%s' (%s)", slot_name, provider_label)
raise HTTPException(
status_code=status.HTTP_500_INTERNAL_SERVER_ERROR,
detail=f"Empty result while {operation} ({provider_label}).",
) from exc
except AdapterPayloadValidationError as exc:
detail = exc.format_first_error()
logger.error("Invalid adapter payload for slot '%s' (%s): %s", slot_name, provider_label, detail)
raise HTTPException(
status_code=status.HTTP_500_INTERNAL_SERVER_ERROR,
detail=f"Unexpected result while {operation} ({provider_label}): {detail}",
) from exc
def parse_api_request_slot(
self,View on GitHub (pinned to 976ec789d2)
Solutions
- Check the server log for 'Payload slot ... is not configured' — it names the exact slot
- Fix the provider integration so it registers the missing PayloadSlot (server-side)
- If using a plugin, update it to the version matching the mapper API
- As an end user: report to the operator — nothing in the request can fix it
Defensive patterns
Strategy: validation
Try / catch
try:
result = await provider_deployment_call(client, ...)
except httpx.HTTPStatusError as e:
if e.response.status_code == 500 and "integration is not configured" in e.response.json()["detail"]:
raise ServerIntegrationError("report to operator; slot missing server-side")
raise Prevention
- Smoke-test every provider operation after installing/upgrading a deployment provider plugin
- Server-side: assert all required PayloadSlots are registered at provider init (fail fast at boot)
- Do not retry — a missing slot never self-heals
When it happens
Trigger: Any deployment API call whose provider adapter returns/builds a payload parsed through a slot the provider never configured — e.g. a new provider subclass that skips defining a response slot, or a provider whose integration setup failed partially.
Common situations: Custom deployment provider plugin incomplete; upgrade changed the slot contract and the provider module was not updated; feature flagged off for this provider's slot.
Related errors
- Empty result while {operation} ({provider_label}).
- Unexpected result while {operation} ({provider_label}): {det
- The {provider_label} integration is not configured for this
- Missing provider_data for {provider_label}.
- Failed to download files: ${response.statusText}
AI-assisted analysis of langflow-ai/langflow@976ec789d2 (2026-08-14).
Data as JSON: /api/errors/af21061affc0250d.
Report an issue: GitHub.