automatelab/automation-error-index huggingface dataset:
Platform: LangChain
Category: install
Error: unexpected keyword argument prompt
Cause: create_react_agent() got an unexpected keyword argument 'prompt' means your installed langgraph predates the state_modifier -to- prompt rename, so upgrade langgraph and langgraph-prebuilt , or pass state_modifier as...
Platform: LangChain
Category: other
Error: LangChain Output Parsing Errors (handle_parsing_errors=True)
Cause: handle_parsing_errors=True only retries the same free-text ReAct loop, so switch the agent to tool calling or a LangGraph create_react_agent instead of patching the parser
Platform: LangChain
Category: schema
Error: LangChain MultiServerMCPClient NotImplementedError on Windows
Cause: If a LangChain MultiServerMCPClient example raises NotImplementedError on Windows the moment it tries to spawn an MCP server over stdio, set the asyncio Proactor policy before anything async runs: import sys, asyncio...
Platform: LangChain
Category: other
Error: Agent stopped due to iteration limit
Cause: The error Agent stopped due to iteration limit or time limit means a LangChain agent ran out of steps before the model emitted a final answer
Platform: LangChain
Category: schema
Error: ValueError: System message must be at beginning of message list.
Affected versions: langchain==0.2.7
Cause: LangGraph appends a system message node after the user message is already in state, but the Anthropic API requires the system message to be first.
Fix: Bind the system prompt directly to the ChatAnthropic model via the system= parameter instead of inserting it as a graph node. Remove any initialize_system_prompt node and its edges. This ensures the system message is always first when sent to the API.
Platform: LangChain
Category: install
Error: ValueError: invalid literal for int() with base 10: '1+1'
Cause: The LangGraph CLI's _parse_version() splits Docker version strings on hyphens only, so a SemVer build-metadata segment like 28.1.1+1 leaves '1+1' as the patch component, which cannot be cast to int.
Fix: Upgrade langgraph-cli to a version with the docker.py parser fix once released. As a workaround, install a Docker release without build metadata (e.g. a plain 28.x.y). The upstream fix splits on '+' before the int cast.
Platform: LangChain
Category: schema
Error: langgraph.errors.InvalidUpdateError: Must write to at least one of [state keys]
Cause: A graph node returns a dict that omits all keys defined in the typed state schema, so LangGraph's write-validation rejects the update.
Fix: Ensure every node returns a dict whose keys match at least one field in your TypedDict state class. Check for typos between the return value and the schema. If a field uses a reducer, verify the reducer accepts the value type the node returns.
Platform: LangChain
Category: config
Error: ValueError: Missing required config key 'store' for conditional edge
Cause: LangGraph does not inject the store dependency into conditional edge functions the way it does for nodes, so an edge function declaring a store parameter receives no value at runtime.
Fix: Remove the store parameter from the conditional edge function. Access store data inside a preceding regular node and pass the result through state instead. Track the upstream fix in LangGraph PR #6425 targeting v1.1.
Platform: Make
Category: config
Error: Make scenario won't trigger: 7-step webhook diagnosis
Cause: When a Make scenario won't trigger, run seven checks in order: scenario active, trigger type understood, webhook queue counter non-zero, URL reachable, incomplete executions cleared, polling reset, schedule timezone...
Platform: Make
Category: timeout
Error: request has exceeded the allotted timeout
Cause: The error fires when any Make module's outbound API call exceeds Make's ~40s connector cap; fix it with a Break error handler for intermittent slowness, or chunk, sleep, or async-redesign the call when the upstream...
Platform: Make
Category: timeout
Error: Make Maximum execution timeout 40 minutes with error handlers
Cause: Make raises ExecutionInterruptedError as a scenario-level warning, so per-module Break or Rollback handlers never catch it; the fix is to enable Incomplete Executions, set Break with auto-retry on the slowest module,...
Platform: Make
Category: timeout
Error: the Make HTTP module 40-second timeout error
Cause: Make's HTTP module times out individual requests at roughly 40 seconds
Platform: Make
Category: auth
Error: Failed to verify connection. Status Code Error: 400
Error code: 400
Cause: The OAuth token for a connection expired or was revoked, most often because the Google Cloud app remains in 'Testing' (7-day token lifetime).
Fix: In Make Connections, reauthorize the affected connection. If it recurs weekly, set the Google OAuth consent screen from 'Testing' to 'In production'. For non-Google services, delete and recreate the connection with fresh credentials.
Platform: Make
Category: auth
Error: Cannot initialize the scenario because of the reason 'Failed to verify connection'
Cause: A module's connection is missing, expired, or lacks scopes, so Make fails the init phase before execution - meaning in-scenario error handlers cannot catch it.
Fix: Check every module has a connection selected. Reauthorize any invalid connections in the Connections panel, or delete and recreate with the required scopes. Confirm the third-party API key/OAuth app has not been revoked or had scopes reduced.
Platform: Make
Category: auth
Error: Cannot initialize the scenario because of the reason 'Failed to verify account. Please try again later.'
Cause: Make's platform-side account verification to a third-party service fails transiently during the scenario init phase, logging 0 operations.
Fix: Wait a few minutes and re-run; the error is often transient. If it persists, reauthorize the connection. Add a retry router downstream to handle intermittent init failures without losing data.
Platform: Make
Category: auth
Error: AccountValidationError: Failed to verify connection. access_denied
Cause: The generic HTTP OAuth 2.0 module's token handling does not satisfy a specific API's authorization-code or refresh-token requirements, so the connection looks valid but fails at runtime.
Fix: Switch from the generic HTTP OAuth module to the service's dedicated Make app if one exists. For a custom HTTP connection, inspect request/response headers with the Make DevTool to find the failing OAuth step. Ensure token refresh is configured and the auth code is not reused after expiry.
Platform: Make
Category: timeout
Error: The operation timed out
Cause: A module did not get a response within Make's ~40-second per-module timeout, often from long-running report generation, slow queries, or upstream latency.
Fix: Add an error handler with a Retry directive on the timed-out module. For consistently slow operations, use the API's async/polling endpoint and restructure the scenario to poll for completion. Use the Make DevTool to log response times and tell consistent vs random timeouts apart.
Platform: Make
Category: connectivity
Error: ETIMEDOUT: Service is temporarily unavailable.
Cause: The TCP connection from Make to the target host exceeded the connection timeout - the remote server is unreachable, overloaded, or blocking Make's egress IPs.
Fix: Confirm the target service is online. Allow Make's published egress IPs through the service's firewall/Cloudflare. Add a Retry/Ignore error handler so transient network issues do not fail the scenario permanently. Test the same request from outside Make (e.g. Postman) to isolate the side at fault.
Platform: Make
Category: connectivity
Error: ConnectionError ENOTFOUND: Service is temporarily unavailable.
Cause: DNS resolution for the target hostname failed from Make - a misspelled URL, a changed domain, or a transient DNS outage.
Fix: Check the URL for typos or deprecated subdomains and confirm the current hostname from the service's docs. If correct, wait and retry (DNS propagation/outage). Add a Retry error handler for transient DNS failures.
Platform: Make
Category: config
Error: there is no listening for this webhook
Cause: A payload was sent to a Make webhook URL not attached to any active, enabled scenario, so there is no listener to receive it.
Fix: Check the Webhooks panel to confirm the webhook exists and is linked to an active scenario; recreate it if it was detached or deleted. Update the external service to the correct active URL. If the webhook is retired, delete it so the caller gets a 410 and stops calling.
Platform: Make
Category: config
Error: Webhook was inactive for too long and therefore was removed.
Cause: Make automatically deletes webhooks not connected to any scenario for more than 5 days, removing the endpoint entirely.
Fix: Create a new webhook and update the external service with the new URL. To prevent recurrence, always keep webhooks attached to an active (even paused) scenario; keep occasional scenarios disabled rather than deleting them so the URL stays registered.
Platform: Make
Category: auth
Error: module initialization failed with an error
Cause: During a webhook-triggered scenario's startup, Make verifies all module connections; a broken/expired connection means the webhook never starts and its queue is not drained.
Fix: Find which module's connection failed (check the last successful run's log) and reauthorize or replace it. Because in-scenario error handlers do not fire during init, fix the connection itself. Then run the scenario once manually to confirm the queue starts draining.
Platform: Make
Category: schema
Error: DataError: Invalid item in module output. Expected Object, but found String
Cause: A module returned a plain string (an error message or malformed JSON) where Make expected a structured object - often a wrong endpoint URL or an API returning an HTML error page.
Fix: Verify the module's endpoint URL and that it returns valid JSON. Use the Make DevTool to inspect the raw response - HTML/plain text means the endpoint is wrong or erroring. Fix the URL or parameters and re-run. If incomplete executions are enabled, repair the stored data after fixing.
Platform: Make
Category: connectivity
Error: Failed to verify connection. service is temporarily unavailable
Cause: Make's connection-verification call to a third-party OAuth/API endpoint got no response or a server error, indicating an outage or maintenance on the remote service.
Fix: Check the third-party service's status page. Wait for the outage to clear, then reauthorize. Add a retry error handler so transient availability issues do not permanently halt the scenario. If outages are frequent, add a fallback endpoint or a connection monitor.
Platform: Make
Category: timeout
Error: Cannot initialize scenario: 'The operation timed out'
Cause: Make's init phase (before any module runs) failed because an external service did not respond in time, often with slow watch-trigger endpoints like email or DB polling.
Fix: Recheck the polling module's config (IMAP settings, SQL connection string) for wrong addresses/ports causing slow handshakes. Replace the module with a fresh instance of the same type. If intermittent, disable and re-enable the scenario to force Make to re-establish the watch connection.
Platform: Make
Category: schema
Error: Source is not valid JSON
Cause: The Parse JSON module received a non-JSON string - commonly AI output wrapped in markdown code fences, or an Array Aggregator output not first converted to a string.
Fix: If from an AI module, add a text-replace step to strip the ```json and ``` fences before Parse JSON. If from an Array Aggregator, pass it through join() (or map()+join()) to produce a proper JSON string first.
Platform: Make
Category: config
Error: 400: INVALID_ARGUMENT - Unable to parse range
Error code: 400
Cause: The Google Sheets module's stored sheet name no longer matches the actual tab - it was renamed, or it references the document title instead of the sheet name.
Fix: Open the Google Sheets module and re-select the Spreadsheet, then re-select the Sheet Name so it refreshes to the current tab. Avoid special characters (brackets, hyphens) in tab names. If the range is hardcoded, verify it uses the tab name not the document name.
Platform: Make
Category: schema
Error: Validation failed for 1 parameter(s). Missing value of required parameter 'key'
Cause: A required parameter in a downstream module is mapped to the wrong upstream variable, or the upstream module produced no output so the mapped variable is empty.
Fix: Open the failing module and re-check each mapped field references the correct bundle from the correct upstream module. Run step-by-step and inspect each module's output bundle before mapping. Add a filter/Router before the module so it only proceeds when the required value is present.
Platform: Make
Category: schema
Error: Collection can't be converted to text for parameter 'value'
Cause: A field expecting plain text is receiving an entire collection/array - the mapped variable points to a parent collection instead of a scalar field within it.
Fix: Expand the mapped variable and select the specific child field (e.g. item.name not item). If the upstream returns an array, use map() to extract the scalar field or join() to flatten to a string before passing it on.
Platform: Make
Category: schema
Error: Failed to parse request body as JSON: unexpected EOF
Error code: 400
Cause: The HTTP module is sending the JSON payload as query parameters or raw text rather than a typed JSON body, so the receiving API sees an incomplete request.
Fix: In the HTTP 'Make a Request' module, set Body type to 'JSON (application/json)' and put the payload in the Request content field as valid JSON. Do not use Query String fields for body data. Validate the JSON against the API docs before re-running.
Platform: Make
Category: schema
Error: Response body is not a valid JSON. Bad control character in string literal in JSON
Cause: The external API returned a response containing a raw control character (unescaped newline/tab/binary) inside a JSON string, failing strict parsing.
Fix: Turn off 'Parse response' in the HTTP module to receive the raw body as a string, then feed it to a Parse JSON module (its parser may tolerate minor issues). If it still fails, use a text-transform to strip/replace the offending characters first. Report the malformed response to the API provider.
Platform: Make
Category: config
Error: [400] Invalid JSON payload received. Proto field is not repeating, cannot start list.
Error code: 400
Cause: A multi-value array is passed to a Google API field that expects a single object, so the serializer emits a list the proto definition forbids.
Fix: Open the module and check each field is not receiving a mapped array variable. Use a Text Aggregator or join() to flatten multi-value inputs to a single string before mapping. If intermittent, add an Ignore/Resume route to log the problematic bundle.
Platform: Make
Category: other
Error: IMLError: Cannot read properties of undefined (reading 'match')
Cause: A module received an empty array or undefined value - often because an upstream trigger (e.g. an RSS feed) returned no new items - and tried to process it as structured data.
Fix: Add a Resume error handler so the scenario continues on empty input rather than crashing. Or insert a filter/Router before the module that checks the array is not empty. Run manually to inspect the upstream output bundle and confirm data is present.
Platform: Make
Category: config
Error: Function 'displayError' finished with error! Cannot read properties of undefined (reading 'toString')
Cause: The connected service (commonly WordPress) is returning HTML instead of JSON, typically because a security plugin or firewall blocks Make's IPs from the REST API.
Fix: Whitelist Make's published IP ranges in the server firewall and security plugins (Wordfence, Cloudflare). Confirm the REST API is reachable at {site}/wp-json/. Enable Pretty Permalinks in WordPress. If it persists, temporarily disable security plugins to find the blocking rule.
Platform: Make
Category: config
Error: After adding an Iterator, downstream modules only show 'Value' instead of field names
Cause: Modules added after an Iterator were never executed in sequence before configuring, so Make has not inferred their output schema for mapping.
Fix: Run the scenario after each module addition, not only at the end: run the source, then add and run the Iterator, then add and map downstream modules. If the chain is already built, click 'Run once' on each module top-to-bottom with real data so Make registers the output structure.
Platform: Make
Category: schema
Error: Validation failed for 1 parameter(s). Missing value of required parameter 'name'
Cause: A required text field is mapped to a variable that evaluates to empty/null at runtime because the upstream source did not include that value in the current bundle.
Fix: Add a filter before the module using 'Text > Is not empty' on the mapped variable so the step is skipped when absent. Or set a fallback with the ifempty() function. Run the preceding module in isolation and confirm the field is actually returned.
Platform: Make
Category: schema
Error: Array Aggregator output fails ParseJSON (simple aggregation causes invalid json)
Cause: The Array Aggregator produces an array object, not a JSON string; passing it directly to Parse JSON fails because Parse JSON requires a string input.
Fix: Wrap the aggregator output in join() to produce a comma-separated string (or map()+join() for nested values) before Parse JSON. Validate the result with a JSON validator. For a JSON array string, wrap as '[' + join(array, ',') + ']'.
Platform: Make
Category: auth
Error: Failed to verify connection. Invalid refresh token. Please reauthorize the connection
Cause: An OAuth refresh token expired or was revoked, most commonly because the connected Google Cloud app is still in Testing mode, which caps token lifetime at 7 days.
Fix: In Google Cloud Console, open APIs & Services > OAuth consent screen and PUBLISH APP to move it to Production. Then in Make > Connections, reauthorize the affected connection. Production tokens do not expire weekly, ending the cycle.
Platform: Make
Category: rate-limit
Error: 429 Too Many Requests
Error code: 429
Cause: A module exceeded the connected service's API rate limit by sending too many requests in a short window.
Fix: Add a Sleep module between looping modules (1-2s). For webhook scenarios, enable Sequential Processing so executions do not pile up. For persistent overflow, add a Break error handler so failed bundles queue in Incomplete Executions and retry automatically.
Platform: Make
Category: config
Error: Scenario can not be executed because it has unresolved records in incomplete executions
Cause: Make blocks execution when the Incomplete Executions queue contains unresolved bundles from a previous failed run, to prevent data duplication.
Fix: Open the scenario's Incomplete Executions tab and retry or delete every queued bundle until empty. If it looks empty but the error persists, reload the page (a UI caching bug shows a stale empty state). The scenario then runs normally.
Platform: Make
Category: config
Error: No more credits to execute a scenario
Cause: The organization's monthly operation allowance was fully consumed, pausing all scenarios.
Fix: Buy additional operations from Make billing, or wait for the monthly reset on your plan anniversary. Paused scenarios resume automatically and queued webhooks are processed. Set a usage alert under Organization > Usage to prevent recurrence.
Platform: Make
Category: other
Error: Reason for interruption: Maximum number of repeats exceeded
Cause: A Break error-handler exhausted its configured retry attempts without the failing module succeeding, so Make stops retrying and logs an incomplete execution.
Fix: Open the Break module and raise 'Number of Attempts'. Use the Make DevTool debugger to find which module keeps failing and why (often a downstream API outage). Fix the underlying API issue or add an upstream filter so bad bundles never reach the retrying module.
Platform: OpenAI Agents SDK
Category: config
Error: agents.exceptions.UserError: Hosted tools are not supported with the ChatCompletions API.
Cause: HostedMCPTool (and tools like WebSearchTool) require the Responses API, but the agent was initialised with OpenAIChatCompletionsModel, which uses the Chat Completions endpoint that does not support hosted tools.
Fix: Switch to the default OpenAIResponsesModel (or omit the model argument) so the SDK uses the Responses API. If you must use Chat Completions, replace hosted tools with MCPServerStdio or MCPServerSse local integrations. Do not mix HostedMCPTool with a ChatCompletions-backed model.
Platform: OpenAI Agents SDK
Category: schema
Error: openai.BadRequestError: 400 - No tool output found for function call
Affected versions: openai-agents==0.0.14
Cause: When previous_response_id is passed to Runner.run(), the Responses API expects tool outputs for every function call in that prior response; missing outputs cause a 400.
Fix: Ensure every tool call in the previous response has a corresponding tool output in the input list before passing previous_response_id. As a diagnostic, omit previous_response_id to confirm the cause. Upgrade past v0.0.14 where this was a known issue.
Platform: OpenAI Agents SDK
Category: schema
Error: openai.BadRequestError: 400 'default' is not permitted
Cause: The SDK converts a Pydantic output_type to JSON Schema for response_format, but the OpenAI API forbids 'default' keywords and 'oneOf' constructs that Pydantic generates for defaulted fields or discriminated unions.
Fix: Remove default values from fields in your output_type model, or make them Optional[T] set explicitly in the prompt. For unions, flatten the schema manually rather than using Discriminator. Track the upstream sanitisation fix in SDK issue #474.
Platform: Power Automate
Category: other
Error: Power Automate Triggers Not Firing
Cause: A Power Automate trigger that never fires is almost always a suspended flow, a failed trigger registration ("Fix the trigger"), a broken connection, or a trigger condition that never evaluates true - check those four...
Platform: Power Automate
Category: auth
Error: Power Automate flow 401 / 403 Unauthorized errors
Error code: 401
Cause: A Power Automate cloud flow that returns 401 Unauthorized almost always has an expired connection
Platform: Power Automate
Category: schema
Error: InvalidTemplate. The provided value is of type 'Null'.
Error code: InvalidTemplate
Cause: An expression using dynamic values fails at runtime because the actual data is null when a string, object, or array was expected - not catchable at save time.
Fix: Open the failed run, select the action, and inspect Inputs for the actual value. Guard null-prone references with if(empty(...)) or coalesce() to supply a default. Validate types before conversion (e.g. isInt() before int()). For dates, pass an explicit format to formatDateTime()/parseDateTime().
Platform: Power Automate
Category: schema
Error: InvalidTemplate. Property selection is not supported on values of type 'String'.
Error code: InvalidTemplate
Cause: An expression like item()?['property'] is applied to a plain string instead of an object, often because the dynamic content comes from a different level of the response than expected.
Fix: Inspect the actual action output in run history to confirm the data shape. Adjust the expression to the correct property path (e.g. body('Action')?['value']?['property']). When iterating, ensure the Apply to each input is the array, not a single string element.
Platform: Power Automate
Category: schema
Error: OpenApiOperationParameterValidationFailed. The API operation does not contain a definition for parameter 'item/<FieldInternalName>'.
Error code: OpenApiOperationParameterValidationFailed
Cause: A flow action references a SharePoint/connector field by an internal name that no longer exists or was renamed, so connector schema validation fails.
Fix: Open the failing action and remove the unrecognized field mapping. Re-add the column using its current internal name from SharePoint list settings. If the column was deleted, recreate it or remove the reference. Save and re-run.