errors.json

{
  "name": "AutomateLab Automation Error Index",
  "description": "Catalogued automation error messages with verified fixes, across n8n, Make, Zapier, Cursor, Claude Code, Power Automate and UiPath.",
  "license": "CC-BY-4.0",
  "source": "https://automatelab.tech/products/datasets/automation-error-index/",
  "generated": "2026-05-28",
  "count": 207,
  "platforms": [
    "AutoGen",
    "Claude Code",
    "CrewAI",
    "Cursor",
    "LangChain",
    "Make",
    "OpenAI Agents SDK",
    "Power Automate",
    "UiPath",
    "Zapier",
    "n8n"
  ],
  "categories": [
    "auth",
    "config",
    "connectivity",
    "install",
    "other",
    "rate-limit",
    "schema",
    "timeout",
    "version"
  ],
  "errors": [
    {
      "error": "ValueError: Message type StructuredMessage[AgentResponse] is not registered.",
      "platform": "AutoGen",
      "code": null,
      "versions": [
        "autogen-agentchat>=0.6.4"
      ],
      "category": "version",
      "cause": "Since autogen-agentchat 0.6.4 the Teams integration changed message-type registration; agents using output_content_type add custom StructuredMessage subtypes never registered with the group-chat container, so logging raises ValueError.",
      "fix_url": null,
      "fix_steps": "Downgrade to autogen-agentchat==0.6.2 as a temporary workaround. Remove output_content_type from affected agents if the structured type is not strictly required. Watch issues #6795 and #6983 for an official patch that registers custom message types at group-chat init.",
      "source_url": "https://github.com/microsoft/autogen/issues/6795",
      "source": "mined",
      "published": "",
      "id": "autogen-valueerror-message-type-structuredmessage-agentresponse-"
    },
    {
      "error": "Failed to instantiate component: model_info is required when model name is not a valid OpenAI model",
      "platform": "AutoGen",
      "code": null,
      "versions": [
        "autogen-studio==0.4.2"
      ],
      "category": "config",
      "cause": "AutoGen cannot infer capabilities for non-standard identifiers (Azure deployment names, local models), so it requires an explicit model_info dict when the name does not match a known OpenAI slug.",
      "fix_url": null,
      "fix_steps": "Add a model_info dict specifying capabilities (e.g. {\"vision\": false, \"function_calling\": true, \"json_output\": true}). For Azure OpenAI, pair the deployment name with the matching model_info for the underlying model. See the AutoGen ModelInfo dataclass for required keys.",
      "source_url": "https://github.com/microsoft/autogen/issues/6189",
      "source": "mined",
      "published": "",
      "id": "autogen-failed-to-instantiate-component-model-info-is-required-w"
    },
    {
      "error": "TypeError: create() takes 1 argument(s) but 2 were given",
      "platform": "AutoGen",
      "code": null,
      "versions": [
        "autogen-ext==0.4.5"
      ],
      "category": "config",
      "cause": "MagenticOneGroupChat passes chat.completions from the standard OpenAI client to create(), but the AsyncAzureOpenAI wrapper uses a different signature that rejects the extra positional argument.",
      "fix_url": null,
      "fix_steps": "Pass an AzureOpenAIChatCompletionClient (from autogen_ext.models.openai) instead of extracting service_client.chat.completions directly. Construct it with azure_deployment, azure_endpoint, and api_version. Do not mix the raw Azure OpenAI SDK client with MagenticOne components.",
      "source_url": "https://github.com/microsoft/autogen/issues/5349",
      "source": "mined",
      "published": "",
      "id": "autogen-typeerror-create-takes-1-argument-s-but-2-were-given"
    },
    {
      "id": "claude-code-no-available-ides-detected",
      "error": "No available IDEs detected",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "install",
      "cause": "When /ide in Claude Code reports \"No available IDEs detected\" while Cursor is open on the Windows host but Claude Code is installed inside WSL, relaunch Cursor from inside WSL with cursor",
      "fix_url": "https://automatelab.tech/blog/ai-coding/claude-code-no-available-ides-wsl-cursor/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-21"
    },
    {
      "id": "claude-code-claude-code-creating-a-nul-file-on-windows",
      "error": "Claude Code creating a 'nul' file on Windows",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "If Claude Code keeps dropping a file named nul in your Windows project and Explorer or del nul refuses to remove it, the fix is two commands",
      "fix_url": "https://automatelab.tech/blog/ai-coding/claude-code-nul-file-windows-fix/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-19"
    },
    {
      "id": "claude-code-mcp-token-expired-without-refresh-token-in-claude-co",
      "error": "MCP Token expired without refresh token in Claude Code",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "Claude Code's \"Token expired without refresh token\" is bug #25245 ; delete the stale credential entry, re-authenticate via /mcp , and on macOS grant the Keychain item persistent access",
      "fix_url": "https://automatelab.tech/blog/ai-coding/mcp-token-expired-no-refresh-fix/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-16"
    },
    {
      "id": "claude-code-claude-code-sessionstart-hooks-firing-without-contex",
      "error": "Claude Code SessionStart hooks firing without context",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "If a Claude Code plugin's SessionStart hook fires successfully but Claude never sees the additionalContext (bug #16538), move the hook config out of the plugin's hooks.json and into ~/.claude/settings.json",
      "fix_url": "https://automatelab.tech/blog/ai-coding/claude-code-sessionstart-hook-no-context/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-09"
    },
    {
      "error": "MCP servers failed to connect",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "connectivity",
      "cause": "An MCP server child process is aborted during initialization, often due to a missing API key in keychain or an init timeout before the server responds.",
      "fix_url": null,
      "fix_steps": "Verify your Anthropic API key is set and reachable. Test the MCP server binary directly in a terminal to confirm it starts within the timeout. Create the missing cache directory: mkdir -p ~/Library/Caches/claude-cli-nodejs. If the same config works in Claude Desktop, update Claude Code to the latest version (a known CLI-only bug).",
      "source_url": "https://github.com/anthropics/claude-code/issues/1611",
      "source": "mined",
      "published": "",
      "id": "claude-code-mcp-servers-failed-to-connect"
    },
    {
      "error": "OAuth error: Failed to fetch user roles: OAuth account information not found in config",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "The OAuth flow completes in the browser but Claude Code fails to write or read back the token from the config file.",
      "fix_url": null,
      "fix_steps": "Full reinstall: npm uninstall -g @anthropic-ai/claude-code; rm -rf ~/.claude ~/Library/Application\\ Support/ClaudeCode; npm cache clean --force; npm install -g @anthropic-ai/claude-code; then log in again.",
      "source_url": "https://github.com/anthropics/claude-code/issues/1484",
      "source": "mined",
      "published": "",
      "id": "claude-code-oauth-error-failed-to-fetch-user-roles-oauth-account"
    },
    {
      "error": "API Error: 401 authentication_error: Invalid bearer token",
      "platform": "Claude Code",
      "code": "401",
      "versions": [
        "2.0.28"
      ],
      "category": "auth",
      "cause": "A regression in v2.0.28 made the stored bearer token invalid or unable to refresh, persisting across logout/login.",
      "fix_url": null,
      "fix_steps": "Run 'claude logout' then 'claude login' to force a new token. If it persists, remove ~/.claude/claude.json and any ANTHROPIC_AUTH_TOKEN/ANTHROPIC_BASE_URL env vars, reinstall with npm install -g @anthropic-ai/claude-code, and authenticate again.",
      "source_url": "https://github.com/anthropics/claude-code/issues/10503",
      "source": "mined",
      "published": "",
      "id": "claude-code-api-error-401-authentication-error-invalid-bearer-to"
    },
    {
      "error": "OAuth error: timeout of 15000ms exceeded",
      "platform": "Claude Code",
      "code": null,
      "versions": [
        "2.1.72"
      ],
      "category": "auth",
      "cause": "DNS resolution for auth.anthropic.com fails in certain regions/networks, so the OAuth login request times out after 15 seconds.",
      "fix_url": null,
      "fix_steps": "Confirm auth.anthropic.com resolves with 'nslookup auth.anthropic.com 8.8.8.8'. If not, use a VPN or a different DNS server. Alternatively authenticate via API key by setting ANTHROPIC_API_KEY instead of the browser OAuth flow.",
      "source_url": "https://github.com/anthropics/claude-code/issues/33238",
      "source": "mined",
      "published": "",
      "id": "claude-code-oauth-error-timeout-of-15000ms-exceeded"
    },
    {
      "error": "command not found: claude",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "install",
      "cause": "On macOS with Homebrew-managed Node, npm creates a symlink pointing to the raw JS file rather than the executable launcher, so 'claude' is not on PATH.",
      "fix_url": null,
      "fix_steps": "Remove the broken symlink: rm /opt/homebrew/bin/claude. Create the correct one into the Cellar: ln -s /opt/homebrew/Cellar/node/<version>/bin/claude /opt/homebrew/bin/claude. Verify with 'claude --version'.",
      "source_url": "https://github.com/anthropics/claude-code/issues/3172",
      "source": "mined",
      "published": "",
      "id": "claude-code-command-not-found-claude"
    },
    {
      "error": "Claude Code is not supported on Windows. Claude Code requires macOS or Linux.",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "install",
      "cause": "The npm preinstall script detects Windows when 'npm install' runs from a Windows-side path inside WSL, even though the shell is Linux.",
      "fix_url": null,
      "fix_steps": "Use a true WSL terminal (not PowerShell/CMD) and confirm 'uname -a' reports Linux. Ensure npm is the WSL-side binary ('which npm' under /usr/, not /mnt/c/). If npm is Windows-side, install Node natively in WSL (nvm install --lts), then reinstall: npm install -g @anthropic-ai/claude-code.",
      "source_url": "https://github.com/anthropics/claude-code/issues/188",
      "source": "mined",
      "published": "",
      "id": "claude-code-claude-code-is-not-supported-on-windows-claude-code-"
    },
    {
      "error": "ENOEXEC: posix_spawn '/mnt/c/Windows/System32/reg.exe'",
      "platform": "Claude Code",
      "code": "ENOEXEC",
      "versions": [
        "2.1.108",
        "2.1.118"
      ],
      "category": "install",
      "cause": "Claude Code unconditionally spawns reg.exe on startup for Chrome native-messaging registration; with WSL Windows interop disabled, the file exists at the mount path but cannot execute.",
      "fix_url": null,
      "fix_steps": "If interop must stay disabled, there is no user-side fix as of v2.1.118 - the crash precedes any prompt. As a workaround, temporarily re-enable interop in /etc/wsl.conf ([interop] enabled=true) while launching Claude Code, then disable again. Track the upstream issue for a fix.",
      "source_url": "https://github.com/anthropics/claude-code/issues/52504",
      "source": "mined",
      "published": "",
      "id": "claude-code-enoexec-posix-spawn-mnt-c-windows-system32-reg-exe"
    },
    {
      "error": "/usr/bin/bash: line 1: /c/Users/<name>: Permission denied",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "Claude Code builds a shell state-tracking command with an unquoted path; when the Windows username contains a space, Bash word-splits the path and tries to execute the first token.",
      "fix_url": null,
      "fix_steps": "Rename the Windows user to remove the space, or create a new account without a space and run Claude Code from it. Commands still execute correctly despite the error, so it is cosmetic until an upstream fix ships.",
      "source_url": "https://github.com/anthropics/claude-code/issues/29538",
      "source": "mined",
      "published": "",
      "id": "claude-code-usr-bin-bash-line-1-c-users-name-permission-denied"
    },
    {
      "error": "EACCES: permission denied, mkdir '/tmp/claude/<path>/tasks'",
      "platform": "Claude Code",
      "code": "EACCES",
      "versions": [],
      "category": "other",
      "cause": "Claude Code uses a shared /tmp/claude/ directory owned by the first user who ran it; other users lack write permission to create subdirectories.",
      "fix_url": null,
      "fix_steps": "Recreate with world-writable sticky bit: sudo rm -rf /tmp/claude && sudo mkdir -p /tmp/claude && sudo chmod 1777 /tmp/claude. Alternatively set dangerouslyDisableSandbox: true in .claude/settings.json as a temporary workaround.",
      "source_url": "https://github.com/anthropics/claude-code/issues/16914",
      "source": "mined",
      "published": "",
      "id": "claude-code-eacces-permission-denied-mkdir-tmp-claude-path-tasks"
    },
    {
      "error": "zsh:1: permission denied: /var/folders/.../T/claude-XXXX-cwd",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "Claude Code writes a temporary CWD-tracking file to the system temp directory; after a macOS major upgrade the permissions change and block writes from user processes.",
      "fix_url": null,
      "fix_steps": "Bash commands still execute correctly - this is cosmetic. There is no user-side fix as the temp path is internal. Check for a newer Claude Code release that resolves it and follow the linked issue for a patch.",
      "source_url": "https://github.com/anthropics/claude-code/issues/8896",
      "source": "mined",
      "published": "",
      "id": "claude-code-zsh-1-permission-denied-var-folders-t-claude-xxxx-cw"
    },
    {
      "error": "Stop hook error",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "Claude Code's hook output validator treats zero bytes of output as a missing JSON object and falsely reports a stop-hook failure, even when the hook exits 0.",
      "fix_url": null,
      "fix_steps": "Confirm the hook works by checking its exit code manually - the error is cosmetic for hooks that produce no output and exit 0. As a workaround, emit an empty JSON object from the hook: echo '{}'. Track the upstream fix in the linked issue.",
      "source_url": "https://github.com/anthropics/claude-code/issues/10463",
      "source": "mined",
      "published": "",
      "id": "claude-code-stop-hook-error"
    },
    {
      "error": "[DEBUG] Found 0 hook matchers in settings",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "An extra 'hooks' wrapper object inside each event array makes the hook parser find no valid matchers and silently skip all hook execution.",
      "fix_url": null,
      "fix_steps": "Open ~/.claude/settings.json and remove the intermediate {\"hooks\": [...]} wrapper. Each event key should map directly to an array of hook objects. Run /hooks inside Claude Code to verify hooks are now listed.",
      "source_url": "https://github.com/anthropics/claude-code/issues/11544",
      "source": "mined",
      "published": "",
      "id": "claude-code-debug-found-0-hook-matchers-in-settings"
    },
    {
      "error": "invalid_type expected string received undefined at path protocolVersion",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "Claude Code's MCP init layer drops the protocolVersion field before sending the initialize request to stdio servers, so schema validation fails before any data is sent.",
      "fix_url": null,
      "fix_steps": "Use a wrapper shell script instead of referencing the server directly: export MCP_PROTOCOL_VERSION=2025-03-26 and exec your server binary. Register the wrapper: claude mcp add <name> /path/to/wrapper.sh. This bypasses the internal validation step.",
      "source_url": "https://github.com/anthropics/claude-code/issues/768",
      "source": "mined",
      "published": "",
      "id": "claude-code-invalid-type-expected-string-received-undefined-at-p"
    },
    {
      "error": "Failed to reconnect to MCP server",
      "platform": "Claude Code",
      "code": null,
      "versions": [],
      "category": "connectivity",
      "cause": "Claude Code spawns MCP subprocesses with an unescaped working directory; when its launch directory contains spaces or special characters (e.g. iCloud Drive), spawning fails.",
      "fix_url": null,
      "fix_steps": "Launch Claude Code from a directory whose full path has no spaces or special characters: cd ~/Projects/myproject && claude. The MCP server's own cwd setting does not prevent this - the launch directory of Claude Code itself must be clean. Confirmed upstream bug with no config workaround.",
      "source_url": "https://github.com/anthropics/claude-code/issues/19518",
      "source": "mined",
      "published": "",
      "id": "claude-code-failed-to-reconnect-to-mcp-server"
    },
    {
      "error": "API Error: Rate limit reached (stale cached plan after upgrade)",
      "platform": "Claude Code",
      "code": "429",
      "versions": [
        "2.1.92"
      ],
      "category": "rate-limit",
      "cause": "Claude Code caches subscriptionType and rateLimitTier at login and never refreshes them, so after a plan upgrade the CLI still enforces old limits.",
      "fix_url": null,
      "fix_steps": "Clear the accessToken, refreshToken, expiresAt, subscriptionType, and rateLimitTier fields in ~/.claude/.credentials.json, then run 'claude login' to force a fresh OAuth flow. Verify the correct plan shows in the CLI header before resuming.",
      "source_url": "https://github.com/anthropics/claude-code/issues/43639",
      "source": "mined",
      "published": "",
      "id": "claude-code-api-error-rate-limit-reached-stale-cached-plan-after"
    },
    {
      "error": "API Error: Rate limit reached despite Max subscription and low usage",
      "platform": "Claude Code",
      "code": "429",
      "versions": [
        "2.1.63"
      ],
      "category": "rate-limit",
      "cause": "A corrupted credentials.json (subscriptionType and rateLimitTier both null) makes the CLI enforce API-tier limits even after a successful re-login that shows Max in the header.",
      "fix_url": null,
      "fix_steps": "Run 'claude logout', then delete or zero the subscriptionType and rateLimitTier fields in ~/.claude/.credentials.json. Run 'claude login' and confirm /status shows the correct tier and sane usage. If it persists, wait for the session reset window shown in the error.",
      "source_url": "https://github.com/anthropics/claude-code/issues/29579",
      "source": "mined",
      "published": "",
      "id": "claude-code-api-error-rate-limit-reached-despite-max-subscriptio"
    },
    {
      "id": "crewai-crewai-hierarchical-delegateworktoolschema-validation-err",
      "error": "CrewAI hierarchical DelegateWorkToolSchema validation error",
      "platform": "CrewAI",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "If a CrewAI crew running Process.hierarchical raises 2 validation errors for DelegateWorkToolSchema ..",
      "fix_url": "https://automatelab.tech/blog/ai-agents/crewai-hierarchical-delegateworktoolschema-validation-error-0114/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-11"
    },
    {
      "error": "ValidationError: 1 validation error for Task - expected_output Field required",
      "platform": "CrewAI",
      "code": null,
      "versions": [
        "crewai>=0.19"
      ],
      "category": "schema",
      "cause": "The CrewAI Task model marks expected_output as required with no default; omitting it (or a Pydantic 2.8+ alias edge case) raises a ValidationError at instantiation.",
      "fix_url": null,
      "fix_steps": "Always pass an explicit expected_output string when constructing a Task. If the error appears even when present, pin pydantic<2.8 as a temporary workaround for the upstream alias-handling bug. Upgrade CrewAI once a patch is released.",
      "source_url": "https://github.com/crewAIInc/crewAI/issues/973",
      "source": "mined",
      "published": "",
      "id": "crewai-validationerror-1-validation-error-for-task-expected-outp"
    },
    {
      "error": "AttributeError: _ARRAY_API not found; ImportError: numpy.core.multiarray failed to import",
      "platform": "CrewAI",
      "code": null,
      "versions": [],
      "category": "install",
      "cause": "A transitive dependency (typically onnxruntime) was compiled against NumPy 1.x and cannot load under NumPy 2.x, which removed the legacy numpy.core namespace.",
      "fix_url": null,
      "fix_steps": "Downgrade NumPy with pip install 'numpy<2' as an immediate fix, or upgrade onnxruntime to a NumPy-2-compatible build. Check compiled deps with pip list | grep onnx and update any that predate NumPy 2 support.",
      "source_url": "https://github.com/crewAIInc/crewAI/issues/2431",
      "source": "mined",
      "published": "",
      "id": "crewai-attributeerror-array-api-not-found-importerror-numpy-core"
    },
    {
      "error": "click.exceptions.Abort: You are missing the 'mcp' package",
      "platform": "CrewAI",
      "code": null,
      "versions": [],
      "category": "install",
      "cause": "MCPServerAdapter.__init__() calls click.confirm() interactively when the mcp package is absent, which aborts in non-TTY environments like FastAPI, Docker, and CI.",
      "fix_url": null,
      "fix_steps": "Install the package: pip install mcp crewai-tools[mcp]. In headless environments, ensure mcp is in your requirements file so MCPServerAdapter never reaches the prompt. Track the upstream fix (raise ImportError instead of prompting) in CrewAI issue #3163.",
      "source_url": "https://github.com/crewAIInc/crewAI/issues/3163",
      "source": "mined",
      "published": "",
      "id": "crewai-click-exceptions-abort-you-are-missing-the-mcp-package"
    },
    {
      "id": "cursor-agent-execution-timed-out",
      "error": "Agent Execution Timed Out",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "timeout",
      "cause": "After upgrading to Cursor 3, Jupyter notebooks refuse to open and the AI panel throws Agent Execution Timed Out because of a stale extension cache; delete %APPDATA%\\Cursor\\CachedExtensions and restart",
      "fix_url": "https://automatelab.tech/blog/ai-coding/cursor-3-jupyter-agent-execution-timed-out-fix/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-15"
    },
    {
      "id": "cursor-cursor-rules-not-loading-4-causes-and-how-to-fix-each",
      "error": "Cursor rules not loading: 4 causes and how to fix each",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "Cursor reads project rules from .cursor/rules/<name>.mdc at the repository root",
      "fix_url": "https://automatelab.tech/blog/ai-coding/cursor-rules-not-loading-fix/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-07"
    },
    {
      "error": "We've hit a rate limit with the provider. Please switch to the 'auto' model, another model, or try again in a few moments.",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "rate-limit",
      "cause": "Cursor's upstream AI provider temporarily throttled requests due to high demand or plan-level throughput limits.",
      "fix_url": null,
      "fix_steps": "Switch the active model to 'auto' or a different model in the model picker. Wait 30-60 seconds and retry. If it persists, check your provider's usage dashboard for quota exhaustion. A higher Cursor/provider tier increases throughput.",
      "source_url": "https://forum.cursor.com/t/weve-hit-a-rate-limit-with-the-provider-please-switch-to-the-auto-model-another-model-or-try-again-in-a-few-moments-request-id-0f6c18ed-7a67-4672-8375-17d168f8093c/137327",
      "source": "mined",
      "published": "",
      "id": "cursor-we-ve-hit-a-rate-limit-with-the-provider-please-switch-to"
    },
    {
      "error": "User API Key Rate limit exceeded",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "rate-limit",
      "cause": "Cursor relays the rate-limit from the upstream provider when a BYOK key exhausts its requests-per-minute or token quota, which Agent mode can hit quickly via parallel tool calls.",
      "fix_url": null,
      "fix_steps": "Wait for the provider's rate-limit window to reset (usually 60s). Check your tier's RPM/TPM limits on the provider dashboard. In Settings > Models, reduce Agent concurrency or switch to a higher-quota model. Upgrade the provider tier if Agent workloads routinely hit the cap.",
      "source_url": "https://forum.cursor.com/t/user-provided-api-key-rate-limit-exceeded/18576",
      "source": "mined",
      "published": "",
      "id": "cursor-user-api-key-rate-limit-exceeded"
    },
    {
      "error": "Authentication blocked, please contact your admin",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "The Auth0 sign-in flow detects a policy restriction - an org SSO/email-domain block, a school/work network firewall, or a flagged account - and rejects the attempt.",
      "fix_url": null,
      "fix_steps": "Try signing in with a personal email (Gmail/GitHub) not subject to the blocked domain. Allowlist cursor.com / auth.cursor.sh in corporate SSO or firewall settings. If a school/work email, ask IT to whitelist auth.cursor.sh. If the account is flagged, email hi@cursor.sh with the details.",
      "source_url": "https://forum.cursor.com/t/authentication-blocked-please-contact-your-admin/117526",
      "source": "mined",
      "published": "",
      "id": "cursor-authentication-blocked-please-contact-your-admin"
    },
    {
      "error": "Codebase indexing failed",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "Background indexing cannot complete due to an oversized repo, a network/TLS failure, low disk space, or a corrupted local index cache.",
      "fix_url": null,
      "fix_steps": "Add large generated dirs (node_modules, dist, .git) to a .cursorignore. Ensure 5+ GB free disk. Run 'Cursor: Reindex Codebase' from the Command Palette. If it persists, close Cursor, delete the index cache (macOS ~/Library/Application Support/Cursor/User/globalStorage; Windows %APPDATA%\\Cursor\\User\\globalStorage), and reopen.",
      "source_url": "https://forum.cursor.com/t/codebase-indexing-failed-no-way-to-fix/30522",
      "source": "mined",
      "published": "",
      "id": "cursor-codebase-indexing-failed"
    },
    {
      "error": "Connection failed. If the problem persists, please check your internet connection or VPN",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "connectivity",
      "cause": "Cursor cannot reach its backend API servers, most often because a VPN, corporate proxy, or firewall is intercepting or blocking the TLS connection.",
      "fix_url": null,
      "fix_steps": "Disconnect the VPN and retry. In Settings search 'HTTP/2' and enable 'Disable HTTP/2', then restart. Behind a corporate proxy, set the proxy under Settings > Network Proxy and whitelist api2.cursor.sh. Check Cursor's status page for incidents.",
      "source_url": "https://forum.cursor.com/t/connection-failed-if-the-problem-persists-please-check-your-internet-connection-or-vpn/64673",
      "source": "mined",
      "published": "",
      "id": "cursor-connection-failed-if-the-problem-persists-please-check-yo"
    },
    {
      "error": "Your conversation is too long. Please try creating a new conversation or shortening your messages",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "The accumulated tokens in the current chat (files, tool outputs, history) exceeded the model's context window.",
      "fix_url": null,
      "fix_steps": "Start a fresh chat (Cmd/Ctrl+N) and reference only the needed files. Remove large @file/@codebase attachments no longer relevant. Break long multi-step tasks into separate chats. If it fires in a new chat, check no very large files are auto-attached via .cursorrules.",
      "source_url": "https://forum.cursor.com/t/your-conversation-is-too-long-please-try-creating-a-new-conversation-or-shortening-your-messages/36171",
      "source": "mined",
      "published": "",
      "id": "cursor-your-conversation-is-too-long-please-try-creating-a-new-c"
    },
    {
      "error": "The agent execution provider did not respond within 4 seconds. The extension host may be unresponsive.",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "Cursor's extension host process stops responding - often after an update or on resource-constrained machines - preventing the Agent from invoking tools.",
      "fix_url": null,
      "fix_steps": "Run 'Developer: Restart Extension Host' from the Command Palette. If that fails, quit and relaunch Cursor. Run 'cursor --disable-extensions' to isolate a crashing third-party extension. If still broken, reinstall from cursor.com/downloads (partial-update corruption).",
      "source_url": "https://forum.cursor.com/t/the-agent-execution-provider-did-not-respond-within-4-seconds-this-may-indicate-the-extension-host-is-not-running-or-is-unresponsive/148822",
      "source": "mined",
      "published": "",
      "id": "cursor-the-agent-execution-provider-did-not-respond-within-4-sec"
    },
    {
      "error": "Waiting for extension host",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "On startup (often after an update or inside WSL/Remote-SSH), Cursor's extension host fails to initialise, leaving the editor stuck loading.",
      "fix_url": null,
      "fix_steps": "Run 'Developer: Reload Window' from the Command Palette. Launch with 'cursor --disable-extensions' to find a conflicting extension. For WSL, verify the cursor-server binaries inside WSL are not outdated (reconnect Remote-SSH). As a last resort, reinstall the latest build from cursor.com/downloads.",
      "source_url": "https://forum.cursor.com/t/after-last-update-stuck-at-waiting-for-extension-host/149538",
      "source": "mined",
      "published": "",
      "id": "cursor-waiting-for-extension-host"
    },
    {
      "error": "Please update to the latest version of Cursor at cursor.com/downloads to continue using the Agent",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "version",
      "cause": "Cursor's backend enforces a minimum client version; older builds lack the API surface current agent tooling needs and are blocked from new Agent sessions.",
      "fix_url": null,
      "fix_steps": "Download and install the latest release from cursor.com/downloads, then fully restart. If auto-update is stuck, manually download the installer and run it over the existing installation.",
      "source_url": "https://forum.cursor.com/t/update-to-continue-using-the-agent/132956",
      "source": "mined",
      "published": "",
      "id": "cursor-please-update-to-the-latest-version-of-cursor-at-cursor-c"
    },
    {
      "error": "The model does not work with your current plan or API key",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "The selected model is restricted to a higher tier, usage-based billing is off, or a BYOK key is routed through an incorrect base URL.",
      "fix_url": null,
      "fix_steps": "In Settings > Models, select a model your plan supports (free tier excludes several frontier models). Under API Keys, disable 'Override OpenAI Base URL' if enabled (it breaks Anthropic key routing). Enable usage-based billing for on-demand premium models. Verify the BYOK key is in the correct provider field.",
      "source_url": "https://forum.cursor.com/t/does-not-work-with-your-current-plan-or-api-key/148745",
      "source": "mined",
      "published": "",
      "id": "cursor-the-model-does-not-work-with-your-current-plan-or-api-key"
    },
    {
      "error": "We encountered an issue when using your API key: Provider was unable to process your request",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "The provider rejected the request at the API level - typically because 'Override OpenAI Base URL' is enabled while using an Anthropic key, sending a malformed request to the wrong endpoint.",
      "fix_url": null,
      "fix_steps": "In Settings > Models > API Keys, turn off 'Override OpenAI Base URL'. Confirm the key is in the correct provider field with no whitespace. Test the key independently (curl or the provider playground) to rule out a revoked/quota-exhausted key. If a 400, confirm the model name is one the key's org can access.",
      "source_url": "https://forum.cursor.com/t/we-encountered-an-issue-when-using-your-api-key-provider-was-unable-to-process-your-request/142193",
      "source": "mined",
      "published": "",
      "id": "cursor-we-encountered-an-issue-when-using-your-api-key-provider-"
    },
    {
      "error": "Error: invalid api key provided",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "The stored API key is malformed, contains invisible whitespace from a browser copy, has been revoked, or is in the wrong provider field.",
      "fix_url": null,
      "fix_steps": "Delete the key in Settings > Models > API Keys and retype/paste it as plain text from the provider dashboard, with no leading/trailing spaces or newlines. Verify the key is active and not revoked. Ensure it is in the field matching its provider (Cursor has separate inputs per provider).",
      "source_url": "https://forum.cursor.com/t/error-invalid-api-key-provided/148383",
      "source": "mined",
      "published": "",
      "id": "cursor-error-invalid-api-key-provided"
    },
    {
      "error": "AI features broken: ECONNRESET stuck on local proxy 127.0.0.1",
      "platform": "Cursor",
      "code": "ECONNRESET",
      "versions": [],
      "category": "connectivity",
      "cause": "Cursor's traffic is intercepted by a local proxy (Clash, v2ray) on localhost that resets the TCP connection, blocking all AI API calls.",
      "fix_url": null,
      "fix_steps": "Pause or exit the local proxy and restart Cursor to test recovery. In Settings, enable 'Disable HTTP/2' and restart. If the proxy is required, point Cursor's network proxy setting at the correct address rather than relying on system-wide interception. Check the proxy logs for TLS inspection/cert pinning blocking Cursor.",
      "source_url": "https://forum.cursor.com/t/bug-ai-features-completely-broken-econnreset-stuck-on-local-proxy-127-0-0-1-port-10809/152454",
      "source": "mined",
      "published": "",
      "id": "cursor-ai-features-broken-econnreset-stuck-on-local-proxy-127-0-"
    },
    {
      "error": "Bad User API key / Unauthorized User API key",
      "platform": "Cursor",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "The 'Override OpenAI Base URL' toggle routes Anthropic API requests through OpenAI's endpoint, so auth fails even with a valid key.",
      "fix_url": null,
      "fix_steps": "Go to Settings > Models > API Keys and turn OFF 'Override OpenAI Base URL'. Restart Cursor, open a new chat, select a Claude model, and retry. If the toggle re-enables, disable it again and confirm it stays off before each session.",
      "source_url": "https://forum.cursor.com/t/anthropic-claude-api-key-not-working-in-cursor-always-returns-bad-user-api-key-unauthorized/145423",
      "source": "mined",
      "published": "",
      "id": "cursor-bad-user-api-key-unauthorized-user-api-key"
    },
    {
      "error": "This model does not support tools. Please select a different model and try again",
      "platform": "Cursor",
      "code": null,
      "versions": [
        "1.2.2"
      ],
      "category": "config",
      "cause": "Agent mode routed a request to a model (e.g. o3) that does not expose a tool-calling API, often triggered automatically after the previous model hit a usage limit mid-session.",
      "fix_url": null,
      "fix_steps": "Restart Cursor to clear the stale model assignment. If it recurs, open Settings > Models and explicitly select a tool-capable model (claude-3-7-sonnet, gpt-4o) before starting an agent session. Avoid relying on automatic model fallback near usage limits.",
      "source_url": "https://forum.cursor.com/t/this-model-does-not-support-tools-please-select-a-different-model-and-try-again/116039",
      "source": "mined",
      "published": "",
      "id": "cursor-this-model-does-not-support-tools-please-select-a-differe"
    },
    {
      "id": "langchain-langchain-multiservermcpclient-notimplementederror-on-",
      "error": "LangChain MultiServerMCPClient NotImplementedError on Windows",
      "platform": "LangChain",
      "code": null,
      "versions": [],
      "category": "schema",
      "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...",
      "fix_url": "https://automatelab.tech/blog/ai-agents/langchain-multiservermcpclient-notimplementederror-windows/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-10"
    },
    {
      "id": "langchain-agent-stopped-due-to-iteration-limit",
      "error": "Agent stopped due to iteration limit",
      "platform": "LangChain",
      "code": null,
      "versions": [],
      "category": "other",
      "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",
      "fix_url": "https://automatelab.tech/blog/ai-agents/langchain-agent-iteration-limit-error-fix/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-06"
    },
    {
      "error": "ValueError: System message must be at beginning of message list.",
      "platform": "LangChain",
      "code": null,
      "versions": [
        "langchain==0.2.7"
      ],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://github.com/langchain-ai/langgraph/issues/982",
      "source": "mined",
      "published": "",
      "id": "langchain-valueerror-system-message-must-be-at-beginning-of-mess"
    },
    {
      "error": "ValueError: invalid literal for int() with base 10: '1+1'",
      "platform": "LangChain",
      "code": null,
      "versions": [],
      "category": "install",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://github.com/langchain-ai/langgraph/issues/5965",
      "source": "mined",
      "published": "",
      "id": "langchain-valueerror-invalid-literal-for-int-with-base-10-1-1"
    },
    {
      "error": "langgraph.errors.InvalidUpdateError: Must write to at least one of [state keys]",
      "platform": "LangChain",
      "code": null,
      "versions": [],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://github.com/langchain-ai/langgraph/issues/740",
      "source": "mined",
      "published": "",
      "id": "langchain-langgraph-errors-invalidupdateerror-must-write-to-at-l"
    },
    {
      "error": "ValueError: Missing required config key 'store' for conditional edge",
      "platform": "LangChain",
      "code": null,
      "versions": [],
      "category": "config",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://github.com/langchain-ai/langgraph/issues/6340",
      "source": "mined",
      "published": "",
      "id": "langchain-valueerror-missing-required-config-key-store-for-condi"
    },
    {
      "id": "make-request-has-exceeded-the-allotted-timeout",
      "error": "request has exceeded the allotted timeout",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "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...",
      "fix_url": "https://automatelab.tech/blog/no-code/make-request-exceeded-allotted-timeout/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-28"
    },
    {
      "id": "make-make-maximum-execution-timeout-40-minutes-with-error-handle",
      "error": "Make Maximum execution timeout 40 minutes with error handlers",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "timeout",
      "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,...",
      "fix_url": "https://automatelab.tech/blog/no-code/make-max-execution-timeout-40-minutes/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-26"
    },
    {
      "id": "make-the-make-http-module-40-second-timeout-error",
      "error": "the Make HTTP module 40-second timeout error",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "timeout",
      "cause": "Make's HTTP module times out individual requests at roughly 40 seconds",
      "fix_url": "https://automatelab.tech/blog/no-code/make-http-module-40s-timeout/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-08"
    },
    {
      "error": "Failed to verify connection. Status Code Error: 400",
      "platform": "Make",
      "code": "400",
      "versions": [],
      "category": "auth",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/failed-to-verify-connection-my-twitter-oauth-2-0-connection-status-code-error-400/30369",
      "source": "mined",
      "published": "",
      "id": "make-failed-to-verify-connection-status-code-error-400"
    },
    {
      "error": "Cannot initialize the scenario because of the reason 'Failed to verify connection'",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "auth",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/error-frequent-cannot-initialize-the-scenario-because-of-the-reason-failed-to-verify-connection-integromat-google-account/10833",
      "source": "mined",
      "published": "",
      "id": "make-cannot-initialize-the-scenario-because-of-the-reason-failed"
    },
    {
      "error": "Cannot initialize the scenario because of the reason 'Failed to verify account. Please try again later.'",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "Make's platform-side account verification to a third-party service fails transiently during the scenario init phase, logging 0 operations.",
      "fix_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/how-to-prevent-failed-to-verify-account-please-try-again-later/62892",
      "source": "mined",
      "published": "",
      "id": "make-cannot-initialize-the-scenario-because-of-the-reason-failed-2"
    },
    {
      "error": "AccountValidationError: Failed to verify connection. access_denied",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "auth",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/oauth-2-0-request-fails-with-failed-to-verify-connection/59145",
      "source": "mined",
      "published": "",
      "id": "make-accountvalidationerror-failed-to-verify-connection-access-d"
    },
    {
      "error": "The operation timed out",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "timeout",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/random-error-the-operation-timed-out/53015",
      "source": "mined",
      "published": "",
      "id": "make-the-operation-timed-out"
    },
    {
      "error": "ETIMEDOUT: Service is temporarily unavailable.",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "connectivity",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/http-module-keeps-get-warning-etimedout-service-is-temporarily-unavailable/47190",
      "source": "mined",
      "published": "",
      "id": "make-etimedout-service-is-temporarily-unavailable"
    },
    {
      "error": "ConnectionError ENOTFOUND: Service is temporarily unavailable.",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "connectivity",
      "cause": "DNS resolution for the target hostname failed from Make - a misspelled URL, a changed domain, or a transient DNS outage.",
      "fix_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/connectionerror-enotfound-service-is-temporarily-unavailable-ilovepdf/30781",
      "source": "mined",
      "published": "",
      "id": "make-connectionerror-enotfound-service-is-temporarily-unavailabl"
    },
    {
      "error": "there is no listening for this webhook",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "config",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://help.make.com/fix-general-errors",
      "source": "mined",
      "published": "",
      "id": "make-there-is-no-listening-for-this-webhook"
    },
    {
      "error": "Webhook was inactive for too long and therefore was removed.",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "Make automatically deletes webhooks not connected to any scenario for more than 5 days, removing the endpoint entirely.",
      "fix_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/automatically-disabling-webhooks/11724",
      "source": "mined",
      "published": "",
      "id": "make-webhook-was-inactive-for-too-long-and-therefore-was-removed"
    },
    {
      "error": "module initialization failed with an error",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "auth",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://help.make.com/fix-general-errors",
      "source": "mined",
      "published": "",
      "id": "make-module-initialization-failed-with-an-error"
    },
    {
      "error": "DataError: Invalid item in module output. Expected Object, but found String",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/dataerror-invalid-item-in-module-output-expected-object-but-found-string/79580",
      "source": "mined",
      "published": "",
      "id": "make-dataerror-invalid-item-in-module-output-expected-object-but"
    },
    {
      "error": "Failed to verify connection. service is temporarily unavailable",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "connectivity",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/odd-failed-to-verify-connection-service-is-temporarily-unavailable-message-with-an-airtable-connection/103524",
      "source": "mined",
      "published": "",
      "id": "make-failed-to-verify-connection-service-is-temporarily-unavaila"
    },
    {
      "error": "Cannot initialize scenario: 'The operation timed out'",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "timeout",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/cannot-initialize-scenario-the-operation-timed-out/11760",
      "source": "mined",
      "published": "",
      "id": "make-cannot-initialize-scenario-the-operation-timed-out"
    },
    {
      "error": "Source is not valid JSON",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/parse-json-module-source-is-not-valid-json/39650",
      "source": "mined",
      "published": "",
      "id": "make-source-is-not-valid-json"
    },
    {
      "error": "400: INVALID_ARGUMENT - Unable to parse range",
      "platform": "Make",
      "code": "400",
      "versions": [],
      "category": "config",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/400-invalid-argument-unable-to-parse-range/61877",
      "source": "mined",
      "published": "",
      "id": "make-400-invalid-argument-unable-to-parse-range"
    },
    {
      "error": "Validation failed for 1 parameter(s). Missing value of required parameter 'key'",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/error-when-trying-to-retrieve-a-record-from-a-datastore/20655",
      "source": "mined",
      "published": "",
      "id": "make-validation-failed-for-1-parameter-s-missing-value-of-requir"
    },
    {
      "error": "Collection can't be converted to text for parameter 'value'",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/bundlevalidationerror/4479",
      "source": "mined",
      "published": "",
      "id": "make-collection-can-t-be-converted-to-text-for-parameter-value"
    },
    {
      "error": "Failed to parse request body as JSON: unexpected EOF",
      "platform": "Make",
      "code": "400",
      "versions": [],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/failed-to-parse-request-body-as-json/51868",
      "source": "mined",
      "published": "",
      "id": "make-failed-to-parse-request-body-as-json-unexpected-eof"
    },
    {
      "error": "Response body is not a valid JSON. Bad control character in string literal in JSON",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "The external API returned a response containing a raw control character (unescaped newline/tab/binary) inside a JSON string, failing strict parsing.",
      "fix_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/response-body-is-not-a-valid-json/67502",
      "source": "mined",
      "published": "",
      "id": "make-response-body-is-not-a-valid-json-bad-control-character-in-"
    },
    {
      "error": "[400] Invalid JSON payload received. Proto field is not repeating, cannot start list.",
      "platform": "Make",
      "code": "400",
      "versions": [],
      "category": "config",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/400-invalid-json-payload-received/17666",
      "source": "mined",
      "published": "",
      "id": "make-400-invalid-json-payload-received-proto-field-is-not-repeat"
    },
    {
      "error": "IMLError: Cannot read properties of undefined (reading 'match')",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "other",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/cannot-read-properties-of-undefined-reading-match-sheets/65872",
      "source": "mined",
      "published": "",
      "id": "make-imlerror-cannot-read-properties-of-undefined-reading-match"
    },
    {
      "error": "Function 'displayError' finished with error! Cannot read properties of undefined (reading 'toString')",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "config",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/the-operation-failed-with-an-error-function-displayerror-finished-with-error-cannot-read-properties-of-undefined-reading-tostring/69023",
      "source": "mined",
      "published": "",
      "id": "make-function-displayerror-finished-with-error-cannot-read-prope"
    },
    {
      "error": "After adding an Iterator, downstream modules only show 'Value' instead of field names",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "Modules added after an Iterator were never executed in sequence before configuring, so Make has not inferred their output schema for mapping.",
      "fix_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/cannot-map-fields-after-iterator/103405",
      "source": "mined",
      "published": "",
      "id": "make-after-adding-an-iterator-downstream-modules-only-show-value"
    },
    {
      "error": "Validation failed for 1 parameter(s). Missing value of required parameter 'name'",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/validation-failed-for-1-parameter-s-missing-value-of-required-parameter-name/14215",
      "source": "mined",
      "published": "",
      "id": "make-validation-failed-for-1-parameter-s-missing-value-of-requir-2"
    },
    {
      "error": "Array Aggregator output fails ParseJSON (simple aggregation causes invalid json)",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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, ',') + ']'.",
      "source_url": "https://community.make.com/t/simple-aggregation-causes-invalid-json/42965",
      "source": "mined",
      "published": "",
      "id": "make-array-aggregator-output-fails-parsejson-simple-aggregation-"
    },
    {
      "error": "Failed to verify connection. Invalid refresh token. Please reauthorize the connection",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "auth",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/connection-expires-every-7-days-invalid-refresh-token-please-reauthorize-the-connection/55119",
      "source": "mined",
      "published": "",
      "id": "make-failed-to-verify-connection-invalid-refresh-token-please-re"
    },
    {
      "error": "429 Too Many Requests",
      "platform": "Make",
      "code": "429",
      "versions": [],
      "category": "rate-limit",
      "cause": "A module exceeded the connected service's API rate limit by sending too many requests in a short window.",
      "fix_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/error-429-or-rate-limit-error/36445",
      "source": "mined",
      "published": "",
      "id": "make-429-too-many-requests"
    },
    {
      "error": "Scenario can not be executed because it has unresolved records in incomplete executions",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "Make blocks execution when the Incomplete Executions queue contains unresolved bundles from a previous failed run, to prevent data duplication.",
      "fix_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/error-scenario-can-not-be-executed-despite-empty-incomplete-executions/69355",
      "source": "mined",
      "published": "",
      "id": "make-scenario-can-not-be-executed-because-it-has-unresolved-reco"
    },
    {
      "error": "No more credits to execute a scenario",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "The organization's monthly operation allowance was fully consumed, pausing all scenarios.",
      "fix_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/no-more-operations-to-execute-a-scenario/36444",
      "source": "mined",
      "published": "",
      "id": "make-no-more-credits-to-execute-a-scenario"
    },
    {
      "error": "Reason for interruption: Maximum number of repeats exceeded",
      "platform": "Make",
      "code": null,
      "versions": [],
      "category": "other",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://community.make.com/t/error-reason-for-interruption-maximum-number-of-repeats-exceeded/98799",
      "source": "mined",
      "published": "",
      "id": "make-reason-for-interruption-maximum-number-of-repeats-exceeded"
    },
    {
      "error": "agents.exceptions.UserError: Hosted tools are not supported with the ChatCompletions API.",
      "platform": "OpenAI Agents SDK",
      "code": null,
      "versions": [],
      "category": "config",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://github.com/openai/openai-agents-python/issues/1008",
      "source": "mined",
      "published": "",
      "id": "openai-agents-sdk-agents-exceptions-usererror-hosted-tools-are-n"
    },
    {
      "error": "openai.BadRequestError: 400 - No tool output found for function call",
      "platform": "OpenAI Agents SDK",
      "code": null,
      "versions": [
        "openai-agents==0.0.14"
      ],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://github.com/openai/openai-agents-python/issues/673",
      "source": "mined",
      "published": "",
      "id": "openai-agents-sdk-openai-badrequesterror-400-no-tool-output-foun"
    },
    {
      "error": "openai.BadRequestError: 400 'default' is not permitted",
      "platform": "OpenAI Agents SDK",
      "code": null,
      "versions": [],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://github.com/openai/openai-agents-python/issues/474",
      "source": "mined",
      "published": "",
      "id": "openai-agents-sdk-openai-badrequesterror-400-default-is-not-perm"
    },
    {
      "id": "power-automate-power-automate-flow-401-403-unauthorized-errors",
      "error": "Power Automate flow 401 / 403 Unauthorized errors",
      "platform": "Power Automate",
      "code": "401",
      "versions": [],
      "category": "auth",
      "cause": "A Power Automate cloud flow that returns 401 Unauthorized almost always has an expired connection",
      "fix_url": "https://automatelab.tech/blog/rpa/fix-power-automate-flow-401-403-unauthorized/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-07"
    },
    {
      "error": "InvalidTemplate. The provided value is of type 'Null'.",
      "platform": "Power Automate",
      "code": "InvalidTemplate",
      "versions": [],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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().",
      "source_url": "https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-automate/flow-run-issues/getting-errors-null-fields",
      "source": "mined",
      "published": "",
      "id": "power-automate-invalidtemplate-the-provided-value-is-of-type-nul"
    },
    {
      "error": "InvalidTemplate. Property selection is not supported on values of type 'String'.",
      "platform": "Power Automate",
      "code": "InvalidTemplate",
      "versions": [],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://learn.microsoft.com/en-us/answers/questions/5189395/power-automate-error-unable-to-process-template-la",
      "source": "mined",
      "published": "",
      "id": "power-automate-invalidtemplate-property-selection-is-not-support"
    },
    {
      "error": "OpenApiOperationParameterValidationFailed. The API operation does not contain a definition for parameter 'item/<FieldInternalName>'.",
      "platform": "Power Automate",
      "code": "OpenApiOperationParameterValidationFailed",
      "versions": [],
      "category": "schema",
      "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_url": null,
      "fix_steps": "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.",
      "source_url": "https://powerusers.microsoft.com/t5/Building-Flows/Error-when-trying-to-create-an-item-in-sharepoint-with-multi/td-p/327401",
      "source": "mined",
      "published": "",
      "id": "power-automate-openapioperationparametervalidationfailed-the-api"
    },
    {
      "error": "InvalidRequestContent. The request content was invalid and could not be deserialized.",
      "platform": "Power Automate",
      "code": "InvalidRequestContent",
      "versions": [],
      "category": "schema",
      "cause": "A required field in the action payload (commonly the approval assignedTo, or an attachment property) is null or uses an incorrect property name.",
      "fix_url": null,
      "fix_steps": "Check the run detail to see which field is null/malformed. For approvals, ensure Assigned To has a valid user email and is never blank. For attachments, use the content property formatted as {\"name\": \"<file>\", \"content\": \"<base64>\"}. Re-run after fixing the payload.",
      "source_url": "https://powerusers.microsoft.com/t5/Building-Flows/Error-during-Approval-step-InvalidRequestContent/td-p/893129",
      "source": "mined",
      "published": "",
      "id": "power-automate-invalidrequestcontent-the-request-content-was-inv"
    },
    {
      "error": "ConnectionAuthorizationFailed. The caller does not have the minimum required permission on connection.",
      "platform": "Power Automate",
      "code": "ConnectionAuthorizationFailed",
      "versions": [],
      "category": "auth",
      "cause": "The flow maker or running account lacks permission to use one of the connections referenced in the flow.",
      "fix_url": null,
      "fix_steps": "In My Flows, open the flow > Edit > Connections and re-authorize or replace any connection with a warning icon with one owned by or shared with the running user. In solutions, update the connection reference. Verify the user has at least the Environment Maker role.",
      "source_url": "https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-apps/connections/best-practices-when-updating-a-flow",
      "source": "mined",
      "published": "",
      "id": "power-automate-connectionauthorizationfailed-the-caller-does-not"
    },
    {
      "error": "Resource not found for the segment '<EntitySetName>'.",
      "platform": "Power Automate",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "A Dataverse action references an entity set name or custom process action that is incorrect, misspelled, or inactive.",
      "fix_url": null,
      "fix_steps": "Confirm the logical collection (plural) name by opening the table in a Solution > See solution layers. Use the exact logical collection name (e.g. cr123_customentities, not 'Custom Entities'). If it is a custom process action, verify it is Active under Settings > Processes. Re-save and test.",
      "source_url": "https://powerusers.microsoft.com/t5/Microsoft-Dataverse/Resource-not-found-for-the-segment/m-p/1222562",
      "source": "mined",
      "published": "",
      "id": "power-automate-resource-not-found-for-the-segment-entitysetname"
    },
    {
      "error": "Principal user is missing prvCreate<EntityName> privilege.",
      "platform": "Power Automate",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "The service account or user running the Dataverse action has a security role lacking the required Create/Read/Write privilege on the target table.",
      "fix_url": null,
      "fix_steps": "In Power Platform admin center > Users + permissions > Users, select the user and Manage security roles. Assign a role with the required privilege on the target table (Basic User is often the baseline). Re-run; use Run diagnostics on the user to confirm privileges.",
      "source_url": "https://powerusers.microsoft.com/t5/Microsoft-Dataverse/Error-Principal-team-is-missing-prvRead-Entity-privilege/td-p/946036",
      "source": "mined",
      "published": "",
      "id": "power-automate-principal-user-is-missing-prvcreate-entityname-pr"
    },
    {
      "error": "The Dataverse Database for this environment is not ready yet.",
      "platform": "Power Automate",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "Approval flows auto-provision a Dataverse database on first run; that provisioning is still in progress or has failed.",
      "fix_url": null,
      "fix_steps": "In Power Platform admin center, confirm the environment's Dataverse database shows Ready. If provisioning failed, recreate the database or open a support ticket. Once Ready, rerun the flow. Ensure the running user has a Power Automate per-user/per-flow license to satisfy provisioning prerequisites.",
      "source_url": "https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-automate/approvals/flow-approval-cds-provisioning-errors",
      "source": "mined",
      "published": "",
      "id": "power-automate-the-dataverse-database-for-this-environment-is-no"
    },
    {
      "error": "Create an approval action failed. Possible cause could be invalid users assigned for approval.",
      "platform": "Power Automate",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "The email passed to an approval's Assigned To field does not correspond to a valid user in the organization's Azure AD.",
      "fix_url": null,
      "fix_steps": "Verify the email is a licensed Microsoft 365 user in the same tenant; guest accounts need the tenant to allow guest approvals. Replace hard-coded addresses with dynamic content from a trigger/lookup and test with a known-valid internal address. Confirm the user is not deleted/disabled in Azure AD.",
      "source_url": "https://powerusers.microsoft.com/t5/Building-Flows/Help-with-addressing-approval-action-failure/td-p/1828208",
      "source": "mined",
      "published": "",
      "id": "power-automate-create-an-approval-action-failed-possible-cause-c"
    },
    {
      "error": "Flow run timed out. Please try again.",
      "platform": "Power Automate",
      "code": null,
      "versions": [],
      "category": "timeout",
      "cause": "The Power Automate UI timed out waiting for a response; the flow itself is usually still running in the background (a UI-side timeout, not a cancellation).",
      "fix_url": null,
      "fix_steps": "Check My Flows > Run history - the flow likely still ran or succeeded. If an action is genuinely slow, reduce its retry policy from the default 8 retries to a custom policy (e.g. 3 retries, 5s). For flows over 30 days, split long segments into child flows via Run Child Flow.",
      "source_url": "https://learn.microsoft.com/en-us/answers/questions/5129348/power-automate-my-flows-scheduled-error-flow-run-t",
      "source": "mined",
      "published": "",
      "id": "power-automate-flow-run-timed-out-please-try-again"
    },
    {
      "error": "MailboxNotEnabledForRESTAPI. The mailbox is either inactive, soft-deleted, or hosted on-premise.",
      "platform": "Power Automate",
      "code": "MailboxNotEnabledForRESTAPI",
      "versions": [],
      "category": "config",
      "cause": "The Office 365 Outlook connector cannot reach the mailbox because it is on-premises Exchange, lacks an Exchange Online license, or was soft-deleted.",
      "fix_url": null,
      "fix_steps": "Confirm the user has an active Microsoft 365 license including Exchange Online. If on-premises, configure Exchange hybrid and enable the REST endpoint, or migrate to Exchange Online. Re-authorize the Outlook connector after assigning the license to refresh the token.",
      "source_url": "https://learn.microsoft.com/en-us/answers/questions/1657546/how-to-fix-mailboxnotenabledforrestapi",
      "source": "mined",
      "published": "",
      "id": "power-automate-mailboxnotenabledforrestapi-the-mailbox-is-either"
    },
    {
      "error": "Your flow has been suspended because it is in violation of your organization's Data Loss Prevention policies.",
      "platform": "Power Automate",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "A DLP policy classifies two or more connectors used in the flow in different data groups (Business vs Non-Business), suspending the flow automatically.",
      "fix_url": null,
      "fix_steps": "In Power Platform admin center > Data policies, find the policy affecting your environment and identify the offending connector combination. With an admin, move the connectors into the same data group or create an environment-specific policy permitting the combination. Then turn the flow back on.",
      "source_url": "https://learn.microsoft.com/en-us/answers/questions/5707651/power-automate-flow-suspended-due-to-dlp-violation",
      "source": "mined",
      "published": "",
      "id": "power-automate-your-flow-has-been-suspended-because-it-is-in-vio"
    },
    {
      "error": "Send an HTTP request to SharePoint failed: Cannot find resource for the request.",
      "platform": "Power Automate",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "The SharePoint REST URI points to a list, library, or resource that does not exist at the specified relative URL.",
      "fix_url": null,
      "fix_steps": "Double-check the relative URL (e.g. _api/web/lists/GetByTitle('<ExactListTitle>')) - the title is case-sensitive. Confirm the list/library was not renamed. If the site URL changed, update the Site Address. Test _api/web/lists in a browser to enumerate available lists.",
      "source_url": "https://powerusers.microsoft.com/t5/General-Power-Automate/Send-an-HTTP-request-to-SharePoint-Cannot-find-resource-for-the/td-p/1984115",
      "source": "mined",
      "published": "",
      "id": "power-automate-send-an-http-request-to-sharepoint-failed-cannot-"
    },
    {
      "error": "HTTP request failed: A connection attempt failed because the connected party did not properly respond.",
      "platform": "Power Automate",
      "code": null,
      "versions": [],
      "category": "connectivity",
      "cause": "The HTTP action could not establish a TCP connection within the timeout, typically because the host is unreachable, firewalled, or slow.",
      "fix_url": null,
      "fix_steps": "Verify the target URL is publicly reachable and not firewall-blocked; whitelist Power Automate outbound IPs if behind a corporate firewall. Confirm the endpoint supports TLS 1.2+. Configure a custom retry policy and higher timeout on the HTTP action. For on-premises endpoints, use the on-premises data gateway.",
      "source_url": "https://powerusers.microsoft.com/t5/General-Power-Automate/Http-request-failed-the-server-did-not-respond-within-the/td-p/2087164",
      "source": "mined",
      "published": "",
      "id": "power-automate-http-request-failed-a-connection-attempt-failed-b"
    },
    {
      "error": "OpenApiOperationParameterValidationFailed. SendEmailV2 is missing required property 'Attachments/ContentBytes'.",
      "platform": "Power Automate",
      "code": "OpenApiOperationParameterValidationFailed",
      "versions": [],
      "category": "schema",
      "cause": "The Send an email (V2) Attachments array is missing the ContentBytes property, usually because the attachment object was built without all required fields.",
      "fix_url": null,
      "fix_steps": "Construct each attachment with both Name and ContentBytes: {\"Name\": \"<file>\", \"ContentBytes\": \"<base64>\"}. Use outputs('Get_file_content')['body/$content'] for the base64 content. Do not mix ContentBytes (V2) with the older Content property. Test by sending to yourself first.",
      "source_url": "https://powerusers.microsoft.com/t5/General-Power-Automate/Form-attachment-attaching-to-approval-but-not-to-email/td-p/2426966",
      "source": "mined",
      "published": "",
      "id": "power-automate-openapioperationparametervalidationfailed-sendema"
    },
    {
      "error": "ExpressionEvaluationFailed: the result of the evaluation of 'if' condition expression is not boolean",
      "platform": "Power Automate",
      "code": "ExpressionEvaluationFailed",
      "versions": [],
      "category": "schema",
      "cause": "An expression using dynamic values fails at runtime because the actual data is a different type or null — something the engine cannot catch at save time.",
      "fix_url": null,
      "fix_steps": "Open the failed run, select the action, and inspect Inputs for the actual value. Guard null-prone references with if(empty(...)) or coalesce(). Validate types before conversion (e.g. isInt() before int()). For dates, pass an explicit format to formatDateTime()/parseDateTime().",
      "source_url": "https://learn.microsoft.com/en-us/power-automate/error-reference",
      "source": "mined",
      "published": "",
      "id": "power-automate-expressionevaluationfailed-the-result-of-the-eval"
    },
    {
      "error": "ActionFailed: An action failed. No dependent actions succeeded",
      "platform": "Power Automate",
      "code": "ActionFailed",
      "versions": [],
      "category": "other",
      "cause": "A connector action returned a 4xx/5xx from the downstream API, or a called child flow failed; Power Automate wraps the real error in this generic status.",
      "fix_url": null,
      "fix_steps": "Open the failed run and expand the action's Outputs to read the real API error and status code, then fix per status (400 bad input, 404 missing, 5xx downstream). To run an action even after a prior failure, set 'Configure run after' to include 'has failed'. For child flows, drill into the child run history.",
      "source_url": "https://learn.microsoft.com/en-us/answers/questions/1707720/an-action-failed-no-dependent-actions-succeeded",
      "source": "mined",
      "published": "",
      "id": "power-automate-actionfailed-an-action-failed-no-dependent-action"
    },
    {
      "error": "Rate limit is exceeded. Try again in N seconds",
      "platform": "Power Automate",
      "code": "429",
      "versions": [],
      "category": "rate-limit",
      "cause": "The connector enforced its per-timeframe throughput quota (HTTP 429); each connector sets its own limit independent of the daily API request quota.",
      "fix_url": null,
      "fix_steps": "Set the action's Retry Policy to Exponential Interval to back off on 429. Honor any Retry-After header with a Delay in a Do Until loop. Reduce call frequency by filtering data upstream; for Dataverse, review Service Protection limits and batch with ExecuteMultiple.",
      "source_url": "https://learn.microsoft.com/en-us/power-automate/guidance/coding-guidelines/understand-limits",
      "source": "mined",
      "published": "",
      "id": "power-automate-rate-limit-is-exceeded-try-again-in-n-seconds"
    },
    {
      "error": "FlowRunQuotaExceeded: too many requests were made at the same time",
      "platform": "Power Automate",
      "code": "FlowRunQuotaExceeded",
      "versions": [],
      "category": "rate-limit",
      "cause": "The user/tenant consumed all daily Power Platform API request actions for their license tier (e.g. 6,000/day seeded, 40,000/day Premium).",
      "fix_url": null,
      "fix_steps": "Check consumption in Power Platform admin center > Analytics. Cut actions per run: replace Apply to Each with Select/Filter array, add OData $filter/$top to Get items, reduce polling frequency. If the workload needs it, upgrade to a Premium/Process license; short term, spread runs across flows or off-peak.",
      "source_url": "https://learn.microsoft.com/en-us/power-automate/error-reference",
      "source": "mined",
      "published": "",
      "id": "power-automate-flowrunquotaexceeded-too-many-requests-were-made-"
    },
    {
      "id": "uipath-uipath-studio-2024-10-1-eeui-1603-install-error",
      "error": "UiPath Studio 2024.10.1 EEUI / 1603 install error",
      "platform": "UiPath",
      "code": "1603",
      "versions": [
        "2024.10.1"
      ],
      "category": "install",
      "cause": "The EEUI - InitializeEmbeddedUI failure with MSI exit 1603 on UiPath Studio 2024.10.1 happens when endpoint protection kills rundll32.exe ; whitelist the installer, install .NET 4.8.1 plus ASP.NET Core 8.0, and re-run",
      "fix_url": "https://automatelab.tech/blog/rpa/uipath-studio-2024-10-eeui-initializeembeddedui-install-error/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-24"
    },
    {
      "id": "uipath-globalvariablesnamespace",
      "error": "GlobalVariablesNamespace",
      "platform": "UiPath",
      "code": "CS0246",
      "versions": [],
      "category": "other",
      "cause": "The CS0246 GlobalVariablesNamespace error fires during library compilation at publish time, even though the project runs fine in the Studio designer",
      "fix_url": "https://automatelab.tech/blog/rpa/uipath-studio-cs0246-globalvariablesnamespace-publish-error/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-12"
    },
    {
      "error": "Cannot find the UI element corresponding to this selector",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "The selector recorded at design time no longer matches the live element at runtime, typically because the target renders dynamic attributes (title, idx, aaname) that change between sessions.",
      "fix_url": null,
      "fix_steps": "Open the activity and use Indicate on Screen to re-record against the live app. Anchor to a stable parent and replace volatile attributes with wildcards (*). Increase the activity Timeout for slow-loading pages. Enable SimulateClick/SimulateType to bypass full selector resolution for input activities.",
      "source_url": "https://forum.uipath.com/t/error-cannot-find-the-ui-element-corresponding-to-this-selector-exception-type-selectornotfoundexception/103093",
      "source": "mined",
      "published": "",
      "id": "uipath-cannot-find-the-ui-element-corresponding-to-this-selector"
    },
    {
      "error": "Activity timeout exceeded",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "timeout",
      "cause": "A UI Automation activity could not locate or interact with the target element within its Timeout, usually because the app is slow to render or the robot runs unattended without an active desktop.",
      "fix_url": null,
      "fix_steps": "Increase the activity's Timeout (default 30s). Enable SimulateClick/SimulateType so it works without a visible desktop. Add Wait for Ready: Complete or an explicit delay before the interaction. For unattended robots, ensure the session is logged in and unlocked.",
      "source_url": "https://forum.uipath.com/t/message-activity-timeout-exceeded/126604",
      "source": "mined",
      "published": "",
      "id": "uipath-activity-timeout-exceeded"
    },
    {
      "error": "The process cannot access the file because it is being used by another process",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "An Excel file stays locked by a prior Excel activity or an orphaned Excel.exe because the Application Scope was not closed cleanly, or multiple branches access the same file at once.",
      "fix_url": null,
      "fix_steps": "Wrap all Excel operations in one Excel Application Scope (or Use Excel File) so the handle is released on exit. Avoid Append Range in loops; accumulate rows in a DataTable and write once. Kill lingering Excel processes with a Kill Process activity at the start. Ensure no conflicting Excel instance is open.",
      "source_url": "https://forum.uipath.com/t/ms-excel-overview-cannot-access-the-file-because-it-is-being-used-by-another-process/189079",
      "source": "mined",
      "published": "",
      "id": "uipath-the-process-cannot-access-the-file-because-it-is-being-us"
    },
    {
      "error": "Robot does not exist",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "Orchestrator cannot match the machine's domain\\username to a registered Robot, usually a wrong username in the Robot config or a different domain after a rename/migration.",
      "fix_url": null,
      "fix_steps": "Run 'whoami' on the Robot machine for the exact domain\\username. In Orchestrator, update the Robot record's username to match exactly (Manage Access for Modern folders, or Folder > Robots for Classic). Verify the Machine Key matches Assistant > Preferences > Orchestrator Settings. Reconnect the Assistant.",
      "source_url": "https://forum.uipath.com/t/how-to-troubleshoot-robot-does-not-exist-error/504074",
      "source": "mined",
      "published": "",
      "id": "uipath-robot-does-not-exist"
    },
    {
      "error": "Robot Licensing Failed. There are no available licenses on the server. (#1914)",
      "platform": "UiPath",
      "code": "1914",
      "versions": [],
      "category": "config",
      "cause": "Orchestrator shows no free unattended licenses because duplicate machine entries are consuming slots without releasing them.",
      "fix_url": null,
      "fix_steps": "In Orchestrator > Tenant > Licenses, find duplicate machine entries holding unattended licenses and disable the duplicates, leaving only the correct machine active. If none, toggle the Robot type from Unattended to Attended and back to force a refresh. Re-trigger the job after the heartbeat cycle.",
      "source_url": "https://forum.uipath.com/t/robot-licensing-failed-there-are-no-available-licenses-on-the-server-1914/205496",
      "source": "mined",
      "published": "",
      "id": "uipath-robot-licensing-failed-there-are-no-available-licenses-on"
    },
    {
      "error": "Could not find an asset with this name. Error code: 1002",
      "platform": "UiPath",
      "code": "1002",
      "versions": [],
      "category": "config",
      "cause": "Get Asset/Get Credential cannot find the named asset because it is in a different Orchestrator folder than the process, or the Robot lacks read permission on that folder.",
      "fix_url": null,
      "fix_steps": "Confirm the asset name matches exactly (case-sensitive). Check which folder the asset lives in vs the process's folder. Set the activity's Folder Path property to the correct path (use / for nested). For shared folders, ensure the Robot account has Viewer or higher permission.",
      "source_url": "https://forum.uipath.com/t/could-not-find-an-asset-with-this-name-error-code-1002/397342",
      "source": "mined",
      "published": "",
      "id": "uipath-could-not-find-an-asset-with-this-name-error-code-1002"
    },
    {
      "error": "Add Queue Item: Queue does not exist. Error code: 1002",
      "platform": "UiPath",
      "code": "1002",
      "versions": [],
      "category": "config",
      "cause": "The Add Queue Item activity references a queue name not in the Orchestrator folder the Robot runs under, often after a Classic-to-Modern folder migration.",
      "fix_url": null,
      "fix_steps": "Verify the queue exists in the expected folder. In Studio, set the activity's Orchestrator Folder Path to the exact folder where the queue is defined. Confirm the Robot account has permission to that folder. Republish after correcting folder settings.",
      "source_url": "https://forum.uipath.com/t/add-queue-item-queue-does-not-exist-error-code-1002/276317",
      "source": "mined",
      "published": "",
      "id": "uipath-add-queue-item-queue-does-not-exist-error-code-1002"
    },
    {
      "error": "No connection could be made because the target machine actively refused it",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "connectivity",
      "cause": "The Robot service (Service Mode) cannot reach the Orchestrator HTTPS endpoint because the machine uses an unconfigured proxy, or port 443 is firewall-blocked.",
      "fix_url": null,
      "fix_steps": "Verify the Orchestrator URL is reachable from the machine via a browser and that outbound 443 is open. If behind a proxy, add proxy settings to uipath.config under %ProgramFiles%\\UiPath\\Studio\\. Restart the UiPath Robot Service, then reconnect from the Assistant.",
      "source_url": "https://forum.uipath.com/t/no-connection-could-be-made-connecting-uipath-assistant-to-the-orchestrator-because-the-target-machine-actively-refused-it/502999",
      "source": "mined",
      "published": "",
      "id": "uipath-no-connection-could-be-made-because-the-target-machine-ac"
    },
    {
      "error": "Cannot create unknown type '{http://schemas.uipath.com/workflow/activities}ReadRange'",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "version",
      "cause": "The workflow references the ReadRange (or other Excel/Mail/PDF) activity but the corresponding activities package is missing or not deployed on the Robot machine.",
      "fix_url": null,
      "fix_steps": "In Studio, open Manage Packages and confirm UiPath.Excel.Activities is installed and current. When publishing, ensure dependent packages are in the Orchestrator NuGet feed or the Robot's local package folder. On the Robot, clear the .nuget cache (C:\\Users\\<user>\\.nuget\\packages) to force a fresh download. Re-run.",
      "source_url": "https://forum.uipath.com/t/message-cannot-create-unknown-type-http-schemas-uipath-com-workflow-activities-readrange/126140",
      "source": "mined",
      "published": "",
      "id": "uipath-cannot-create-unknown-type-http-schemas-uipath-com-workfl"
    },
    {
      "error": "Could not load file or assembly 'UiPath.System.Activities, Version=23.4.2.0'",
      "platform": "UiPath",
      "code": null,
      "versions": [
        "23.4.0"
      ],
      "category": "version",
      "cause": "Studio 23.4.0 had a packaging defect where published .nupkg files listed incorrect runtime dependencies in the .nuspec, so the Robot fails to resolve UiPath.System.Activities at execution.",
      "fix_url": null,
      "fix_steps": "Downgrade Studio to 22.10.7 and republish. Or extract the .nupkg, correct the .nuspec dependency entries to the 22.10.7 format, repack, and re-upload. Add the UiPath Official NuGet feed to NuGet.config so the Robot can resolve packages. Upgrade past 23.4.0 once verified.",
      "source_url": "https://forum.uipath.com/t/issue-with-2023-4-0-unable-to-run-code-on-robot-machine-could-not-load-file-or-assembly-uipath-system-activities-version-23-4-2-0/540352",
      "source": "mined",
      "published": "",
      "id": "uipath-could-not-load-file-or-assembly-uipath-system-activities-"
    },
    {
      "error": "RemoteException: Could not load file or assembly '{ProjectName}'. The system cannot find the file specified",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "version",
      "cause": "The Robot machine runs an older UiPath version than the one used to publish, so it cannot resolve the project assembly or its dependencies from the NuGet cache.",
      "fix_url": null,
      "fix_steps": "Upgrade the Robot/Assistant to the same version used in Studio. Clear the Robot's NuGet cache (C:\\Users\\<account>\\.nuget\\packages) and re-trigger so dependencies re-download. If the package relies on custom libraries, ensure those .nupkg are in the Orchestrator feed. Confirm the process version points to the correct package.",
      "source_url": "https://forum.uipath.com/t/robot-failing-when-running-in-orchestrator-remoteexception-wrapping-system-io-filenotfoundexception/500855",
      "source": "mined",
      "published": "",
      "id": "uipath-remoteexception-could-not-load-file-or-assembly-projectna"
    },
    {
      "error": "The type initializer for 'UiPath.NuGet.UiPathUtils' threw an exception",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "The NuGet.Config in the Windows system profile (used by the Robot service account) is missing or malformed, so the Robot cannot initialise its NuGet resolver at job start.",
      "fix_url": null,
      "fix_steps": "Go to C:\\Windows\\System32\\config\\systemprofile\\AppData\\Roaming\\NuGet (or SysWOW64 for 32-bit). Verify NuGet.Config begins with a valid XML declaration. If absent or corrupt, copy a valid one from a user profile or recreate it with the correct feeds. Restart the UiPath Robot Service and re-run.",
      "source_url": "https://forum.uipath.com/t/the-type-initializer-for-uipath-nuget-uipathutils-threw-an-exception/307310",
      "source": "mined",
      "published": "",
      "id": "uipath-the-type-initializer-for-uipath-nuget-uipathutils-threw-a"
    },
    {
      "error": "535: 5.7.3 Authentication unsuccessful",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "UiPath.Mail.Activities above 1.9.5 changed SMTP password transmission to SecureString, rejected by mail servers that do not support secure auth on the configured port/TLS.",
      "fix_url": null,
      "fix_steps": "In Send SMTP Mail Message, try port 587 with SecureConnection 'Auto', or port 25 with 'None'. If using a credential asset, pass the plain-text password. Downgrade UiPath.Mail.Activities to 1.9.5 as a stable workaround, or upgrade to 1.12.2+. Ensure the mail server (Exchange/O365) allows Basic Auth or App Passwords.",
      "source_url": "https://forum.uipath.com/t/smtp-authentication-error-after-version-1-9-5-uipath-mail-activities/329417",
      "source": "mined",
      "published": "",
      "id": "uipath-535-5-7-3-authentication-unsuccessful"
    },
    {
      "error": "You are not authenticated",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "The OAuth2 bearer token used for Orchestrator API calls (via HTTP Request or Start Job) has expired or was generated with incorrect client credentials.",
      "fix_url": null,
      "fix_steps": "Re-generate the access token from the identity token endpoint with valid client_id/client_secret from your Orchestrator External Application. Confirm grant_type 'client_credentials' and correct scope. In Swagger/Postman, click Authorize again. For long automations, refresh the token before its ~1-hour expiry.",
      "source_url": "https://forum.uipath.com/t/orchestrator-api-you-are-not-authenticated/207765",
      "source": "mined",
      "published": "",
      "id": "uipath-you-are-not-authenticated"
    },
    {
      "error": "BusinessRuleException is ambiguous between UiPath.Framework.Activities and UiPath.Core",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "version",
      "cause": "Both UiPath.System.Activities and an older UiPath.Framework.Activities are referenced, each exporting BusinessRuleException, causing an ambiguous-reference compile error in Throw activities.",
      "fix_url": null,
      "fix_steps": "In Manage Packages, remove the legacy UiPath.Framework.Activities if unused. In Throw/Catch activities, fully qualify the type as UiPath.Core.BusinessRuleException. Run Analyze Project to confirm no remaining ambiguity. Republish after clearing the old package.",
      "source_url": "https://forum.uipath.com/t/new-businessruleexception-not-working/52457",
      "source": "mined",
      "published": "",
      "id": "uipath-businessruleexception-is-ambiguous-between-uipath-framewo"
    },
    {
      "error": "RemoteException: Job stopped with an unexpected exit code: 0xC0000005",
      "platform": "UiPath",
      "code": "0xC0000005",
      "versions": [],
      "category": "other",
      "cause": "An access-violation crash, most commonly from a version mismatch between the UiPath Excel activities package and the locally installed Microsoft Excel.",
      "fix_url": null,
      "fix_steps": "In Studio, open Manage Packages and downgrade UiPath.Excel.Activities to a version compatible with your Excel (e.g. 2.8.x to 2.5.x/2.6.x). Re-publish and re-run. If it persists, confirm antivirus/firewall is not blocking UiPath robot processes.",
      "source_url": "https://forum.uipath.com/t/remoteexception-wrapping-system-exception-job-stopped-with-an-unexpected-exit-code-0xc0000005/173595",
      "source": "mined",
      "published": "",
      "id": "uipath-remoteexception-job-stopped-with-an-unexpected-exit-code-"
    },
    {
      "error": "XamlObjectWriterException: Cannot create unknown type (activity)",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "version",
      "cause": "The Robot/Orchestrator runtime runs an older activity package that does not recognise activity types from the newer package used at development time.",
      "fix_url": null,
      "fix_steps": "Align Studio, Robot, and Orchestrator on compatible versions. In Studio's Manage Packages, downgrade UiPath.UIAutomation.Activities and UiPath.System.Activities to versions the Orchestrator supports, re-publish, and re-trigger. If already aligned, clear the Robot's NuGet cache (%userprofile%\\.nuget\\packages\\) to force a fresh download.",
      "source_url": "https://forum.uipath.com/t/run-from-orchestrator-cannot-create-unknown-type-at-system-xaml/241073",
      "source": "mined",
      "published": "",
      "id": "uipath-xamlobjectwriterexception-cannot-create-unknown-type-acti"
    },
    {
      "error": "The given key was not present in the dictionary",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "Code or a queue handler reads a dictionary/queue-item field by a key that does not exist at runtime — misspelled, wrong case, or never populated.",
      "fix_url": null,
      "fix_steps": "Guard access with ContainsKey (If: myDict.ContainsKey(\"KeyName\")) and handle the missing case. Verify exact key names against the queue item schema. Wrap access in Try-Catch on KeyNotFoundException to log the missing key. For REFrameworks, confirm SpecificContent fields are populated before Process Transaction.",
      "source_url": "https://forum.uipath.com/t/the-given-key-was-not-present-in-the-dictionary/17505",
      "source": "mined",
      "published": "",
      "id": "uipath-the-given-key-was-not-present-in-the-dictionary"
    },
    {
      "error": "Could not find file ...\\.nuget\\packages\\...\\Main.xaml",
      "platform": "UiPath",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "On non-persistent VDI/VM environments the robot's NuGet cache is wiped on logoff, so later Orchestrator-triggered runs cannot find the unpacked .xaml files.",
      "fix_url": null,
      "fix_steps": "Confirm by logging off and back on and checking the path. If the cache clears on logoff the image is non-persistent — have IT persist the profile or redirect the NuGet folder to a persistent drive. Short term, run the Robot service under a Windows service account to keep the cache alive. Verify project.json's 'main' points to Main.xaml.",
      "source_url": "https://forum.uipath.com/t/system-exception-could-not-find-file-c-users-username-nuget-packages-project-name-project-version-lib-net45-main-xaml/502814",
      "source": "mined",
      "published": "",
      "id": "uipath-could-not-find-file-nuget-packages-main-xaml"
    },
    {
      "id": "zapier-response-payload-size-exceeded-maximum-allowed-payload-si",
      "error": "Response payload size exceeded maximum allowed payload size (6291556 bytes)",
      "platform": "Zapier",
      "code": "6291556",
      "versions": [],
      "category": "other",
      "cause": "The error \"Response payload size exceeded maximum allowed payload size (6291556 bytes)\" fires when a single Zap step receives more than ~6 MiB of data from the connected app or step",
      "fix_url": "https://automatelab.tech/blog/no-code/zapier-response-payload-size-exceeded-6291556-bytes/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-17"
    },
    {
      "error": "Trigger partner failure",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "connectivity",
      "cause": "The trigger app's API did not respond successfully within Zapier's polling window, due to an outage, quota, throttling, or auth issue on the partner side.",
      "fix_url": null,
      "fix_steps": "Wait for the next poll - Zapier retries and picks up missed records automatically. If it recurs, reconnect the app in the trigger step. Check the partner's status page. For persistent failures, simplify the trigger (fewer filter fields, smaller data sets).",
      "source_url": "https://community.zapier.com/troubleshooting-99/trigger-partner-failure-21131",
      "source": "mined",
      "published": "",
      "id": "zapier-trigger-partner-failure"
    },
    {
      "error": "Invalid API Response: Got a result missing the \"id\" property",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "Zapier's polling dedupe requires every object in a trigger's result array to include a top-level field named exactly 'id'; the API returned objects without one.",
      "fix_url": null,
      "fix_steps": "Switch the trigger to Code Mode and map an existing unique field to id, e.g. return results.map(r => ({ ...r, id: r.recordId })). If items are nested in an envelope, extract the array first. Or set a Deduplication Key in the trigger if the app supports it.",
      "source_url": "https://community.zapier.com/general-discussion-13/invalid-api-response-got-a-result-missing-the-id-property-3102",
      "source": "mined",
      "published": "",
      "id": "zapier-invalid-api-response-got-a-result-missing-the-id-property"
    },
    {
      "error": "Invalid API Response: Results must be an array",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "A polling trigger expected a bare array of items but the API returned a wrapper object (e.g. {\"items\": [...]}) or undefined.",
      "fix_url": null,
      "fix_steps": "Switch the trigger to Code Mode and return just the array, e.g. return bundle.response.data.items. Always return an array even when empty (return [] not null). Re-test the trigger to confirm Zapier accepts the shape.",
      "source_url": "https://community.zapier.com/general-discussion-13/invalid-api-response-results-must-be-an-array-error-10571",
      "source": "mined",
      "published": "",
      "id": "zapier-invalid-api-response-results-must-be-an-array"
    },
    {
      "error": "Task timed out after 160 seconds",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "timeout",
      "cause": "A Zap step (commonly a Google Sheets lookup/update) exceeded Zapier's 160-second limit, usually because the target sheet is too large or complex.",
      "fix_url": null,
      "fix_steps": "Trim unused rows, remove volatile formulas (ARRAYFORMULA, IMPORTRANGE), and archive old data. Use a simple indexed search column (ID/email, not a formula). Consider Zapier Tables or a more targeted API call instead of a large Find/Update. Replay the failed run after simplifying.",
      "source_url": "https://community.zapier.com/troubleshooting-99/how-to-troubleshoot-a-google-sheets-zap-error-task-timed-out-after-160-seconds-51498",
      "source": "mined",
      "published": "",
      "id": "zapier-task-timed-out-after-160-seconds"
    },
    {
      "error": "Invalid Syntax: Only numeric values are allowed",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "Formatter's Number transform received a value with non-numeric characters such as a currency symbol, comma, or a line-item array.",
      "fix_url": null,
      "fix_steps": "Add a Formatter > Text > Replace step before the math step to strip the offending characters. If the input is a line-item array, add Formatter > Line-items > Line-item to Text first to flatten it, then map the cleaned value into the Number transform.",
      "source_url": "https://help.zapier.com/hc/en-us/articles/29027034278541-Formatter-error-Invalid-Syntax-Only-numeric-values-are-allowed",
      "source": "mined",
      "published": "",
      "id": "zapier-invalid-syntax-only-numeric-values-are-allowed"
    },
    {
      "error": "Formatter error: Failed to create a number transform; the app returned \"Invalid Syntax.\"",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "The Formatter Number transform received a value it cannot parse - an empty field, a text string, or mixed content from a prior step.",
      "fix_url": null,
      "fix_steps": "Open the failing run in history and inspect the exact value reaching the Formatter input. Add a Formatter > Text > Replace upstream to remove non-numeric characters. If the field is sometimes empty, add a Filter or Paths step to skip the Formatter when blank.",
      "source_url": "https://community.zapier.com/troubleshooting-99/formatter-error-failed-to-create-a-number-transform-the-app-returned-invalid-syntax-17004",
      "source": "mined",
      "published": "",
      "id": "zapier-formatter-error-failed-to-create-a-number-transform-the-a"
    },
    {
      "error": "Failed to run your JavaScript code - ReferenceError: $ is not defined",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "Code by Zapier runs in Node.js and does not include jQuery, so $ (and $.ajax) are undefined.",
      "fix_url": null,
      "fix_steps": "Replace jQuery-style calls with native fetch: const resp = await fetch(url); const data = await resp.json();. Remove any require('jquery') - the environment cannot install packages.",
      "source_url": "https://community.zapier.com/code-webhooks-52/failed-to-run-your-javascript-code-referenceerror-is-not-defined-24604",
      "source": "mined",
      "published": "",
      "id": "zapier-failed-to-run-your-javascript-code-referenceerror-is-not-"
    },
    {
      "error": "ReferenceError: fetch is not defined",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "The Code by Zapier step runs on a Node.js version older than 18, where global fetch does not exist.",
      "fix_url": null,
      "fix_steps": "Check the Node version in the Code step settings and switch to Node 18+ if available. If you cannot change the runtime, use the https built-in module, or move the request into a custom integration using z.request.",
      "source_url": "https://community.zapier.com/code-webhooks-52/referenceerror-fetch-is-not-defined-23417",
      "source": "mined",
      "published": "",
      "id": "zapier-referenceerror-fetch-is-not-defined"
    },
    {
      "error": "Error: You did not define `output`!",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "The Code by Zapier JavaScript step finished without assigning the required 'output' variable, so Zapier has no data to pass on.",
      "fix_url": null,
      "fix_steps": "Set output to a plain object before the code ends, e.g. output = { result: myValue };. With async/await, use return { result: myValue } from the async function. With callbacks, ensure callback(null, { result }) is always reached, including error branches.",
      "source_url": "https://community.zapier.com/code-webhooks-52/when-using-callback-output-not-defined-when-callback-not-called-5610",
      "source": "mined",
      "published": "",
      "id": "zapier-error-you-did-not-define-output"
    },
    {
      "error": "ReferenceError: input_data is not defined",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "In the Code by Zapier JavaScript step, mapped inputs are exposed as inputData (camelCase), not input_data; the wrong name throws.",
      "fix_url": null,
      "fix_steps": "Rename references from input_data to inputData. Confirm field names match the Input Data panel exactly. Note the Python Code step uses input_data while the JavaScript step uses inputData.",
      "source_url": "https://community.zapier.com/code-webhooks-52/referenceerror-input-data-is-not-defined-14999",
      "source": "mined",
      "published": "",
      "id": "zapier-referenceerror-input-data-is-not-defined"
    },
    {
      "error": "The app returned \"Contact id or email is required\" (422)",
      "platform": "Zapier",
      "code": "422",
      "versions": [],
      "category": "schema",
      "cause": "A required identifier (contact ID or email) was empty or unmapped in the action step, so the destination app rejected the request as unprocessable.",
      "fix_url": null,
      "fix_steps": "Open the action and verify at least one required identifier has a non-empty mapped value. Check the Zap history data-in panel to confirm the mapped field has data for the failing record. Add a Filter before the action to halt when the identifier is blank.",
      "source_url": "https://community.zapier.com/troubleshooting-99/activecampaign-error-the-app-returned-contact-id-or-email-is-required-422-29873",
      "source": "mined",
      "published": "",
      "id": "zapier-the-app-returned-contact-id-or-email-is-required-422"
    },
    {
      "error": "Status Code 400 Bad Request",
      "platform": "Zapier",
      "code": "400",
      "versions": [],
      "category": "schema",
      "cause": "The destination app rejected the request because a required field was missing, empty, or in an unrecognised format (e.g. a name in an email field).",
      "fix_url": null,
      "fix_steps": "Open the Zap history entry, click the failing action, and inspect Data In to find the bad value. Strip optional fields and test with required fields only to isolate the problem field. Add a Formatter to convert the value to the expected format. Re-enable optional fields one at a time.",
      "source_url": "https://community.zapier.com/troubleshooting-99/google-sheets-status-code-400-bad-request-20303",
      "source": "mined",
      "published": "",
      "id": "zapier-status-code-400-bad-request"
    },
    {
      "error": "Trigger partner failure (throttling)",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "rate-limit",
      "cause": "The trigger app is rate-limiting or throttling Zapier's polling requests, causing the trigger poll to fail.",
      "fix_url": null,
      "fix_steps": "Wait for the throttling window to expire; Zapier catches up on the next successful poll. If persistent, reduce polling frequency (a plan with longer intervals) or switch to an instant webhook trigger if the app supports it. Contact the partner if the throttling seems unintended.",
      "source_url": "https://community.zapier.com/troubleshooting-99/trigger-partner-failure-jotform-throttling-22335",
      "source": "mined",
      "published": "",
      "id": "zapier-trigger-partner-failure-throttling"
    },
    {
      "error": "Invalid input JSON when configuring custom request",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "Extra whitespace, a trailing comma, or an unescaped character in the JSON body of a Webhooks/HTTP action made the payload invalid before sending.",
      "fix_url": null,
      "fix_steps": "Paste the JSON body into a validator (e.g. jsonlint.com) to find the syntax error. Remove leading/trailing whitespace and tabs in the field. Ensure dynamically mapped strings that may contain quotes are properly escaped. Save and re-test.",
      "source_url": "https://community.zapier.com/troubleshooting-99/invalid-input-json-when-configuring-custom-request-28698",
      "source": "mined",
      "published": "",
      "id": "zapier-invalid-input-json-when-configuring-custom-request"
    },
    {
      "error": "This auth is expired. Please reconnect it here.",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "The OAuth token for a connected app expired or was revoked, so Zapier lost access to the third-party account.",
      "fix_url": null,
      "fix_steps": "Click the reconnect link, or go to My Apps, find the connection, and click Reconnect with valid credentials. After reconnecting, replay any held runs from Zap History.",
      "source_url": "https://community.zapier.com/troubleshooting-99/salesforce-error-this-auth-is-expired-please-reconnect-it-here-39150",
      "source": "mined",
      "published": "",
      "id": "zapier-this-auth-is-expired-please-reconnect-it-here"
    },
    {
      "error": "Usage of Paths is not allowed for your current plan.",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "Paths is only available on Professional plans and above; enabling a Zap with a Paths step on Free/Starter triggers this error.",
      "fix_url": null,
      "fix_steps": "Upgrade to Professional or higher to use Paths permanently, or start Zapier's free 7-day Paths trial from inside the editor. If you cannot upgrade, replace Paths with individual Filter steps on separate Zaps.",
      "source_url": "https://community.zapier.com/general-questions-3/usage-of-paths-is-not-allowed-for-your-current-plan-error-when-turning-on-zap-8363",
      "source": "mined",
      "published": "",
      "id": "zapier-usage-of-paths-is-not-allowed-for-your-current-plan"
    },
    {
      "error": "Your Zap would not have continued for this test data.",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "The sample data used during testing did not satisfy the Filter/Path condition, so the Zap would have stopped at that step.",
      "fix_url": null,
      "fix_steps": "Compare the filter conditions to the actual sample values - look for hidden spaces, text-vs-number mismatches, or '(missing value)' fields. If you changed the trigger, reload sample data and remap the filter fields. Use 'Contains' instead of 'Exactly matches' when formatting varies. Test with a live record.",
      "source_url": "https://community.zapier.com/troubleshooting-99/your-zap-would-not-have-continued-for-this-test-data-if-this-was-unexpected-edit-or-modify-your-test-record-27982",
      "source": "mined",
      "published": "",
      "id": "zapier-your-zap-would-not-have-continued-for-this-test-data"
    },
    {
      "error": "Your path would not have continued",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "The data in a run did not meet a Paths branch condition, so execution stopped at that branch instead of continuing downstream.",
      "fix_url": null,
      "fix_steps": "Review the branch condition for hidden whitespace, case sensitivity, or array data needing flattening (Formatter > Utilities > Line Items to Text). Test Paths with a live run rather than in isolation. Add a catch-all 'else' path so runs are never silently dropped.",
      "source_url": "https://community.zapier.com/troubleshooting-99/your-path-would-not-have-continued-help-please-23947",
      "source": "mined",
      "published": "",
      "id": "zapier-your-path-would-not-have-continued"
    },
    {
      "error": "Error from Slack: channel_not_found",
      "platform": "Zapier",
      "code": "channel_not_found",
      "versions": [],
      "category": "config",
      "cause": "Slack returned channel_not_found because the connected Zapier account is not in the target channel, the channel was renamed, or a username was passed instead of a channel/member ID.",
      "fix_url": null,
      "fix_steps": "Invite the Zapier bot/user to the channel with /invite @Zapier. For DMs, use the 'Find User by Username' action to get the member ID and map that, not the username. If the channel was renamed, update the field. For private channels, test with a live run.",
      "source_url": "https://community.zapier.com/troubleshooting-99/failed-to-create-a-message-in-slack-error-from-slack-channel-not-found-22525",
      "source": "mined",
      "published": "",
      "id": "zapier-error-from-slack-channel-not-found"
    },
    {
      "error": "Oops! Neither you nor the bot are in the selected channel",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "Both the Zapier Slack bot and the authenticated Slack user are absent from the channel named in the action, so Slack rejects the request.",
      "fix_url": null,
      "fix_steps": "In Slack, open the target channel and type /invite @Zapier to add the bot. Ensure the account used to connect Slack in Zapier is also a member. Re-test after both are confirmed members.",
      "source_url": "https://community.zapier.com/troubleshooting-99/error-when-adding-user-s-to-existing-slack-channel-oops-neither-you-nor-the-bot-are-in-the-selected-channel-46047",
      "source": "mined",
      "published": "",
      "id": "zapier-oops-neither-you-nor-the-bot-are-in-the-selected-channel"
    },
    {
      "error": "There was an error writing to your Google sheet. Unable to parse range",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "Google Sheets rejected the range because the sheet/spreadsheet title has a special character (often a colon), the worksheet was renamed after the Zap was built, or a frozen/hidden/protected row is targeted.",
      "fix_url": null,
      "fix_steps": "Remove colons and special characters from worksheet/spreadsheet titles. If renamed, reselect the spreadsheet and worksheet in the Zap and re-test. Unfreeze/unhide targeted rows/columns. Ensure at least one column value is populated before the Zap fires.",
      "source_url": "https://help.zapier.com/hc/en-us/articles/25804519400461-Google-Sheets-error-There-was-an-error-writing-to-your-Google-Sheets-unable-to-parse-range",
      "source": "mined",
      "published": "",
      "id": "zapier-there-was-an-error-writing-to-your-google-sheet-unable-to"
    },
    {
      "error": "Google Sheets error: Could not find the selected worksheets",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "The Worksheet field needs a worksheet ID, not a name; when the name is passed dynamically Zapier cannot resolve it to a sheet.",
      "fix_url": null,
      "fix_steps": "Add a 'Google Sheets - Find Worksheet' action before the failing step and map its output (the worksheet ID) into the Worksheet field. Do not pass the worksheet name as a dynamic value. For static sheets, pick the worksheet from the dropdown.",
      "source_url": "https://community.zapier.com/troubleshooting-99/google-sheets-error-could-not-find-the-selected-worksheets-41550",
      "source": "mined",
      "published": "",
      "id": "zapier-google-sheets-error-could-not-find-the-selected-worksheet"
    },
    {
      "error": "Webhooks by Zapier: The app returned \"Forbidden\" (403)",
      "platform": "Zapier",
      "code": "403",
      "versions": [],
      "category": "auth",
      "cause": "The target server rejected the webhook with 403 because the API key/Bearer token or auth header is missing, wrong, or lacks permissions.",
      "fix_url": null,
      "fix_steps": "Check the request headers and confirm the Authorization value is current and correctly formatted (e.g. Bearer <token>). Regenerate the key/token if rotated or revoked. Verify the endpoint URL and that the credential can access it. Re-test after updating.",
      "source_url": "https://community.zapier.com/code-webhooks-52/failed-to-create-a-request-in-webhooks-by-zapier-the-app-returned-forbidden-http-status-code-403-26419",
      "source": "mined",
      "published": "",
      "id": "zapier-webhooks-by-zapier-the-app-returned-forbidden-403"
    },
    {
      "error": "Sorry! That is too many emails sent. Please try Mandrill, Mailgun, Gmail, or others for bulk email",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "rate-limit",
      "cause": "The Email by Zapier built-in action hit its account-wide hourly/daily cap (5/day free, 10/hour paid), which applies across all users on the account.",
      "fix_url": null,
      "fix_steps": "Switch from Email by Zapier to a dedicated email app (Gmail, Mailgun, Mailchimp Transactional) with higher volume. If low volume is fine, reduce trigger frequency or add a Filter to limit which records send. For teams, coordinate usage so one user does not exhaust the shared quota.",
      "source_url": "https://help.zapier.com/hc/en-us/articles/23900889722765-Email-by-Zapier-error-Sorry-That-is-too-many-emails-sent-Please-try-Mandrill-Mailgun-Gmail-or-others-for-bulk-email",
      "source": "mined",
      "published": "",
      "id": "zapier-sorry-that-is-too-many-emails-sent-please-try-mandrill-ma"
    },
    {
      "error": "Gmail error: Quota exceeded for quota metric 'Queries' (Queries per minute per user)",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "rate-limit",
      "cause": "Multiple Zaps firing simultaneously exceeded Google's per-user Gmail API quota, so Gmail rate-limits Zapier's requests.",
      "fix_url": null,
      "fix_steps": "Reduce the number of Gmail-triggered/action Zaps running concurrently and remove unnecessary Gmail steps. Replay throttled runs from Zap History after the per-minute quota resets (~60s). For sustained volume, use a Google Workspace account which has higher Gmail API limits than a personal account.",
      "source_url": "https://help.zapier.com/hc/en-us/articles/28741574606093-Gmail-error-Quota-exceeded-for-quota-metric-Queries-and-limit-Queries-per-minute-per-user-of-service-gmail-googleapis-com-for-consumer",
      "source": "mined",
      "published": "",
      "id": "zapier-gmail-error-quota-exceeded-for-quota-metric-queries-queri"
    },
    {
      "error": "The app did not respond in time. It may or may not have completed successfully.",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "timeout",
      "cause": "The connected app took longer than Zapier's ~30s execution window to respond, typically when querying a large dataset or uploading a large file.",
      "fix_url": null,
      "fix_steps": "For triggers, add filters to reduce returned data; for actions, split the work into smaller steps. Reconnect the app account and re-test after a few minutes, since transient slowdowns self-resolve. Enable Autoreplay so Zapier retries the timed-out step automatically.",
      "source_url": "https://community.zapier.com/how-do-i-3/zap-problem-the-app-did-not-respond-in-time-6106",
      "source": "mined",
      "published": "",
      "id": "zapier-the-app-did-not-respond-in-time-it-may-or-may-not-have-co"
    },
    {
      "error": "This [App] step was throttled by Zapier",
      "platform": "Zapier",
      "code": "throttled",
      "versions": [],
      "category": "rate-limit",
      "cause": "Zapier flood-protection triggered because the Zap fired too many runs in a short window (e.g. 100+ tasks queued at once).",
      "fix_url": null,
      "fix_steps": "Add a 'Delay After Queue' step before the throttled action to spread requests. On paid plans, adjust the flood-protection limit in the Zap settings. Replay held runs from Task History once the window passes; for high-volume triggers, split across Zaps or use Looping with a delay.",
      "source_url": "https://help.zapier.com/hc/en-us/articles/8496038845325-Fix-Throttled-by-Zapier-or-Zapier-has-blocked-this-task-errors-in-Zaps",
      "source": "mined",
      "published": "",
      "id": "zapier-this-app-step-was-throttled-by-zapier"
    },
    {
      "error": "This [App] step was held because you've met your plan limits",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "The account consumed its monthly task allowance (or the plan does not support multi-step Zaps), so Zapier pauses further runs.",
      "fix_url": null,
      "fix_steps": "In Settings > Billing, upgrade to a higher task limit or enable pay-per-task. Held runs are not lost — replay them from Zap History once tasks are available. If tasks show available but the error persists, the Zap may use a premium app not in your plan; verify app-tier eligibility.",
      "source_url": "https://community.zapier.com/how-do-i-3/tasks-are-available-but-getting-limit-error-step-was-held-because-you-ve-met-your-plan-limit-2921",
      "source": "mined",
      "published": "",
      "id": "zapier-this-app-step-was-held-because-you-ve-met-your-plan-limit"
    },
    {
      "error": "Halted exception. Nothing could be found for the search",
      "platform": "Zapier",
      "code": "halt",
      "versions": [],
      "category": "schema",
      "cause": "A Search action returned zero results, which Zapier treats as a hard halt unless configured to continue on empty results.",
      "fix_url": null,
      "fix_steps": "In the search action's Configure tab, enable 'Should this step be considered a success when nothing is found?' (or the 'Create record if not found' option). Verify the lookup value matches exactly (spaces, case, numeric vs string). For legitimately-absent data, add a Paths or Filter step to handle the empty branch.",
      "source_url": "https://community.zapier.com/troubleshooting-99/google-sheets-error-halted-exception-nothing-could-be-found-for-the-search-40341",
      "source": "mined",
      "published": "",
      "id": "zapier-halted-exception-nothing-could-be-found-for-the-search"
    },
    {
      "error": "Authentication failed: The app returned \"Invalid API Key\"",
      "platform": "Zapier",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "The stored API key is wrong, expired, or lacks the permissions required by the action.",
      "fix_url": null,
      "fix_steps": "In My Apps, reconnect the affected app and re-enter the key directly from the source app (copy-paste to avoid stray spaces). Confirm the key was not rotated or revoked and that its scopes match the action (read-write vs read-only). If a security/firewall plugin is active (common on WordPress), temporarily disable it to rule out request blocking.",
      "source_url": "https://community.zapier.com/troubleshooting-99/mycred-error-authentication-failed-the-app-returned-invalid-api-key-50497",
      "source": "mined",
      "published": "",
      "id": "zapier-authentication-failed-the-app-returned-invalid-api-key"
    },
    {
      "id": "n8n-requested-version-20250401-is-not-active",
      "error": "Requested version 20250401 is not active",
      "platform": "n8n",
      "code": "20250401",
      "versions": [],
      "category": "auth",
      "cause": "Every n8n LinkedIn node call started returning 426 - {\"status\":426,\"code\":\"NONEXISTENT_VERSION\",\"message\":\"Requested version 20250401 is not active\"} in mid-April 2026 because the node hard-codes a LinkedIn-Version...",
      "fix_url": "https://automatelab.tech/blog/no-code/n8n-linkedin-nonexistent-version-20250401-fix/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-25"
    },
    {
      "id": "n8n-quota-exceeded",
      "error": "Quota exceeded",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "n8n's Google Sheets node returns 429 Quota exceeded once a workflow exceeds 60 reads or 60 writes per minute per Google user; batch the writes, throttle with the Wait node, and stop sharing the n8n Cloud OAuth client",
      "fix_url": "https://automatelab.tech/blog/no-code/n8n-google-sheets-quota-exceeded-fix/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-13"
    },
    {
      "id": "n8n-econnrefused",
      "error": "ECONNREFUSED",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "connectivity",
      "cause": "An ECONNREFUSED error from an n8n HTTP Request node means the target host is reachable on the network but is actively refusing the TCP connection on that port",
      "fix_url": "https://automatelab.tech/blog/no-code/n8n-econnrefused-http-fix/",
      "fix_steps": null,
      "source_url": null,
      "source": "guide",
      "published": "2026-05-05"
    },
    {
      "error": "Problem in node 'HTTP Request' - timeout of 300000ms exceeded",
      "platform": "n8n",
      "code": "ECONNABORTED",
      "versions": [],
      "category": "timeout",
      "cause": "The target API did not respond within n8n's default 5-minute (300000 ms) HTTP timeout window.",
      "fix_url": null,
      "fix_steps": "Open the HTTP Request node, click 'Add Option', and set a higher 'Timeout' value in milliseconds. If the API is genuinely slow, split large payloads into smaller batches with a Loop node so each request completes faster. On self-hosted instances set N8N_HTTP_REQUEST_TIMEOUT to override the global default.",
      "source_url": "https://community.n8n.io/t/http-request-timeout-of-300000ms-exceeded-can-i-extend-timeout/32372",
      "source": "mined",
      "published": "",
      "id": "n8n-problem-in-node-http-request-timeout-of-300000ms-exceeded"
    },
    {
      "error": "Authorization failed - please check your credentials",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "The credential attached to the HTTP Request node is missing, expired, or not sent in the header format the API requires.",
      "fix_url": null,
      "fix_steps": "Confirm the token/key is still valid with the provider. Verify the node's authentication type matches what the API expects (Header Auth, Bearer, Basic). If the credential test passes but execution fails, inject the header manually in the Headers section to bypass the credential layer. Check the raw response body for a more specific message.",
      "source_url": "https://community.n8n.io/t/authorization-failed-please-check-your-credentials/79534",
      "source": "mined",
      "published": "",
      "id": "n8n-authorization-failed-please-check-your-credentials"
    },
    {
      "error": "Request failed with status code 401",
      "platform": "n8n",
      "code": "401",
      "versions": [],
      "category": "auth",
      "cause": "The target API rejected the request because valid authentication credentials were absent or invalid in the headers.",
      "fix_url": null,
      "fix_steps": "Verify the API key/token is correct and not revoked. Ensure the header name matches the API spec (Authorization: Bearer vs x-api-key). For OAuth2, refresh the token and re-save the credential. On self-hosted n8n, confirm DB env vars are set so the internal auth layer initialises.",
      "source_url": "https://community.n8n.io/t/request-failed-with-status-code-401/21605",
      "source": "mined",
      "published": "",
      "id": "n8n-request-failed-with-status-code-401"
    },
    {
      "error": "AxiosError: Request failed with status code 429",
      "platform": "n8n",
      "code": "429",
      "versions": [],
      "category": "rate-limit",
      "cause": "The destination API returns 429 because n8n is sending requests faster than its rate limit allows.",
      "fix_url": null,
      "fix_steps": "Add a Wait node between iterations to space out requests. Enable batching in the HTTP Request node Options with a small batch size. Check your API tier - some providers lower limits when balance drops. For webhook-triggered flows, add queue or debounce logic to avoid bursts.",
      "source_url": "https://community.n8n.io/t/http-request-constantly-returns-response-code-429-axioserror/222258",
      "source": "mined",
      "published": "",
      "id": "n8n-axioserror-request-failed-with-status-code-429"
    },
    {
      "error": "Request failed with status code 403",
      "platform": "n8n",
      "code": "403",
      "versions": [],
      "category": "auth",
      "cause": "The server refuses to authorise the request, commonly because n8n's IP or user-agent is blocked by a WAF/Cloudflare or the API key lacks scope.",
      "fix_url": null,
      "fix_steps": "If the endpoint is behind Cloudflare, add CF-Access-Client-Id/Secret headers or whitelist n8n's IP. Verify the key has the required scopes. Add a realistic User-Agent header to bypass basic bot-detection. On self-hosted n8n, confirm the credential was not overwritten after an upgrade.",
      "source_url": "https://community.n8n.io/t/http-request-blocked-by-cloudflare-403-forbidden-just-a-moment-page/188889",
      "source": "mined",
      "published": "",
      "id": "n8n-request-failed-with-status-code-403"
    },
    {
      "error": "socket hang up",
      "platform": "n8n",
      "code": "ECONNRESET",
      "versions": [],
      "category": "connectivity",
      "cause": "The remote server closed the TCP connection mid-transfer, often when n8n is behind a corporate proxy or the API drops long-lived connections.",
      "fix_url": null,
      "fix_steps": "Behind a corporate proxy, set HTTPS_PROXY/HTTP_PROXY and bootstrap global-agent so Node routes through the proxy; set NO_PROXY for localhost. If intermittent, enable 'Retry On Fail' on the node. On Windows installs, use a .env file with dotenv-cli rather than shell 'set' so variables persist.",
      "source_url": "https://community.n8n.io/t/http-request-node-fails-with-socket-hang-up-behind-corporate-proxy-windows-npm-setup/91957",
      "source": "mined",
      "published": "",
      "id": "n8n-socket-hang-up"
    },
    {
      "error": "self signed certificate",
      "platform": "n8n",
      "code": "DEPTH_ZERO_SELF_SIGNED_CERT",
      "versions": [],
      "category": "connectivity",
      "cause": "The target HTTPS endpoint presents a self-signed certificate that n8n's Node TLS layer rejects because it is not in a trusted CA chain.",
      "fix_url": null,
      "fix_steps": "In the HTTP Request node Options, toggle on 'Ignore SSL Issues'. For nodes lacking that option, set NODE_TLS_REJECT_UNAUTHORIZED=0 as a temporary, private-network-only workaround. For a proper fix, point NODE_EXTRA_CA_CERTS (or SSL_CERT_FILE) at your internal CA bundle.",
      "source_url": "https://community.n8n.io/t/node-http-reqeust-returns-depth-zero-self-signed-cert/19531",
      "source": "mined",
      "published": "",
      "id": "n8n-self-signed-certificate"
    },
    {
      "error": "self-signed certificate in certificate chain",
      "platform": "n8n",
      "code": "SELF_SIGNED_CERT_IN_CHAIN",
      "versions": [],
      "category": "connectivity",
      "cause": "An intermediate certificate in the server's TLS chain is self-signed or issued by a private CA n8n does not trust.",
      "fix_url": null,
      "fix_steps": "Enable 'Ignore SSL Issues' in the HTTP Request node, or 'Allow Unauthorized Certificates' for DB/SMTP nodes. On Docker, mount the internal CA cert and set NODE_EXTRA_CA_CERTS=/path/to/ca.crt in the container. Avoid global NODE_TLS_REJECT_UNAUTHORIZED=0 in production - scope the bypass to the credential.",
      "source_url": "https://community.n8n.io/t/self-signed-certificate-in-certificate-chain/55104",
      "source": "mined",
      "published": "",
      "id": "n8n-self-signed-certificate-in-certificate-chain"
    },
    {
      "error": "unable to verify the first certificate",
      "platform": "n8n",
      "code": "UNABLE_TO_VERIFY_LEAF_SIGNATURE",
      "versions": [],
      "category": "connectivity",
      "cause": "The server's TLS chain is incomplete - the leaf cannot be traced to a trusted root because intermediate certificates are missing.",
      "fix_url": null,
      "fix_steps": "Fix is server-side: configure the web server to serve the full chain including intermediates. Temporarily enable 'Ignore SSL Issues' in the node to confirm the cause. Verify with 'openssl s_client -connect host:443' and look for 'verify error'.",
      "source_url": "https://community.n8n.io/t/unable-to-verify-the-first-certificate-n8n/32686",
      "source": "mined",
      "published": "",
      "id": "n8n-unable-to-verify-the-first-certificate"
    },
    {
      "error": "getaddrinfo ENOTFOUND",
      "platform": "n8n",
      "code": "ENOTFOUND",
      "versions": [],
      "category": "connectivity",
      "cause": "DNS resolution failed - the hostname cannot be resolved to an IP from within the n8n runtime.",
      "fix_url": null,
      "fix_steps": "Confirm the hostname is correct and reachable from the n8n host (nslookup/dig). For Docker, check the container's DNS config or use host networking. For internal hostnames, add to /etc/hosts or use the IP directly. On n8n Cloud, the domain must be publicly resolvable - .local hostnames never resolve.",
      "source_url": "https://community.n8n.io/t/enotfound-error-in-n8n-http-request-node/69973",
      "source": "mined",
      "published": "",
      "id": "n8n-getaddrinfo-enotfound"
    },
    {
      "error": "Maximum number of redirects exceeded",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "connectivity",
      "cause": "The HTTP Request node followed more redirect hops than its limit, often from a redirect loop caused by mismatched OAuth signing URLs or proxy misconfiguration.",
      "fix_url": null,
      "fix_steps": "Ensure the URL used to build auth headers exactly matches the request URL (a mismatch triggers an auth-failure redirect loop). In Options, set 'Follow Redirect' false and 'Ignore Response Code' true to capture the raw redirect for debugging. Check that any proxy is not issuing redirects back to n8n.",
      "source_url": "https://community.n8n.io/t/http-request-node-gives-maximum-number-of-redirects-exceeded-error/14800",
      "source": "mined",
      "published": "",
      "id": "n8n-maximum-number-of-redirects-exceeded"
    },
    {
      "error": "PayloadTooLargeError: request entity too large",
      "platform": "n8n",
      "code": "413",
      "versions": [],
      "category": "config",
      "cause": "The incoming webhook payload exceeds n8n's configured body size limit, so the HTTP layer rejects it before the workflow runs.",
      "fix_url": null,
      "fix_steps": "Set N8N_PAYLOAD_SIZE_MAX to a higher value in MB (e.g. 64) and restart. For large binary uploads also set N8N_DEFAULT_BINARY_DATA_MODE=filesystem. Behind nginx, raise client_max_body_size too. In Docker, add the env var to compose.",
      "source_url": "https://community.n8n.io/t/payloadtoolargeerror-request-entity-too-large-for-100kb-request/7775",
      "source": "mined",
      "published": "",
      "id": "n8n-payloadtoolargeerror-request-entity-too-large"
    },
    {
      "error": "Workflow Webhook Error: Workflow could not be started!",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "The production webhook URL was called but the workflow is not active, or WEBHOOK_URL points to the wrong host so n8n cannot match the request to a registered webhook.",
      "fix_url": null,
      "fix_steps": "Confirm the workflow is saved AND toggled active (required for production URLs). Set WEBHOOK_URL (or N8N_HOST + N8N_PROTOCOL) to the externally reachable base URL. Behind a reverse proxy, set N8N_TRUST_PROXY=true. Deactivate and reactivate to force webhook re-registration.",
      "source_url": "https://community.n8n.io/t/critical-n8n-cloud-production-webhooks-fail-with-workflow-could-not-be-started/200534",
      "source": "mined",
      "published": "",
      "id": "n8n-workflow-webhook-error-workflow-could-not-be-started"
    },
    {
      "error": "Request failed with status code 422",
      "platform": "n8n",
      "code": "422",
      "versions": [],
      "category": "schema",
      "cause": "The API rejected the request because the body or query params failed validation - commonly an expression resolving to the wrong type or an empty value.",
      "fix_url": null,
      "fix_steps": "Inspect the full error response body for the field-level message. Ensure expressions resolve to the expected type; wrap with String(), Number(), or JSON.parse() as needed. For GET requests, make sure no body is sent (older HTTP node versions attached one - upgrade). Use the 'Send Body' toggle to control inclusion.",
      "source_url": "https://community.n8n.io/t/http-get-request-incorrectly-sends-body-causing-422-error-with-fal-ai/192506",
      "source": "mined",
      "published": "",
      "id": "n8n-request-failed-with-status-code-422"
    },
    {
      "error": "invalid_grant: Token has been expired or revoked",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "A Google OAuth2 refresh token is revoked, or the app is in 'Testing' status which limits test-user tokens to a 7-day lifespan.",
      "fix_url": null,
      "fix_steps": "Open the failing credential and click 'Reconnect' for a fresh token. To stop recurrence, set the Google OAuth consent screen to 'In production' (or 'Internal' for Workspace). For non-Google providers, ensure the Auth URI includes any required offline-access parameter.",
      "source_url": "https://community.n8n.io/t/firebase-oauth2-token-has-been-expired-or-revoked/17099",
      "source": "mined",
      "published": "",
      "id": "n8n-invalid-grant-token-has-been-expired-or-revoked"
    },
    {
      "error": "The access token is invalid or has expired",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "The OAuth2 HTTP node cannot auto-refresh because the API never issued a refresh token during the initial authorization.",
      "fix_url": null,
      "fix_steps": "Edit the credential and add the offline-access parameter to the Auth URI (for Google: access_type=offline&prompt=consent), then re-authorise to get a refresh token. If the API has no refresh tokens, store the token externally and inject it via an expression before each request.",
      "source_url": "https://community.n8n.io/t/the-access-token-is-invalid-or-has-expired/11229",
      "source": "mined",
      "published": "",
      "id": "n8n-the-access-token-is-invalid-or-has-expired"
    },
    {
      "error": "ERROR: Unknown top-level item key: pairedItems [item 0]",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "A node (often Google Sheets) emits an invalid 'pairedItems' key that the Code node's strict validator rejects (only json, binary, error, pairedItem, index are allowed).",
      "fix_url": null,
      "fix_steps": "Add a Code node before the failing node to delete the key: for (const item of $input.all()) { delete item.pairedItems; } return $input.all();. Permanently fix by upgrading to n8n v1.18.1+ which resolves the upstream Google Sheets bug.",
      "source_url": "https://community.n8n.io/t/error-unknown-top-level-item-key-paireditems-item-0/33536",
      "source": "mined",
      "published": "",
      "id": "n8n-error-unknown-top-level-item-key-paireditems-item-0"
    },
    {
      "error": "No data found for item-index: \"1\"",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "A downstream node references a previous node with fewer items using legacy $node[] syntax, so index 1+ does not exist in the upstream output.",
      "fix_url": null,
      "fix_steps": "Replace $node[\"NodeName\"].json[\"field\"] with $item(0).$node[\"NodeName\"].json[\"field\"] to pin to a specific item, or use $item($itemIndex) to match each iteration. Better, use the modern $(\"NodeName\").item.json.field syntax which handles pairedItem linking automatically.",
      "source_url": "https://community.n8n.io/t/no-data-found-for-item-index-1/4626",
      "source": "mined",
      "published": "",
      "id": "n8n-no-data-found-for-item-index-1"
    },
    {
      "error": "this.getWorkflowStaticData is not a function",
      "platform": "n8n",
      "code": null,
      "versions": [
        "1.86.0"
      ],
      "category": "other",
      "cause": "The Code node does not expose getWorkflowStaticData on 'this'; it is only available as the global helper $getWorkflowStaticData.",
      "fix_url": null,
      "fix_steps": "Replace this.getWorkflowStaticData('global') with const staticData = $getWorkflowStaticData('global'); in your Code node. See the n8n Code node reference under 'Built-in methods and variables'.",
      "source_url": "https://community.n8n.io/t/code-node-this-getworkflowstaticdata-is-not-a-function-on-v1-86-0-docker-on-windows-persists-after-reinstall/99137",
      "source": "mined",
      "published": "",
      "id": "n8n-this-getworkflowstaticdata-is-not-a-function"
    },
    {
      "error": "n8n may have run out of memory while running this execution",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "The Node.js process exhausts heap memory, often from processing large binary files or accumulating many large items across nodes.",
      "fix_url": null,
      "fix_steps": "Filter or project only needed fields early. Process binary data in chunks/streams rather than whole. Split monolithic workflows into sub-workflows to bound per-execution memory. Self-hosted: raise the heap with NODE_OPTIONS=--max-old-space-size=4096; on Cloud, upgrade to a higher-memory plan.",
      "source_url": "https://community.n8n.io/t/error-execution-stopped-at-this-node-may-have-run-out-of-memory/28362",
      "source": "mined",
      "published": "",
      "id": "n8n-n8n-may-have-run-out-of-memory-while-running-this-execution"
    },
    {
      "error": "The requested webhook is not registered",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "The incoming request's HTTP method does not match the Webhook node's configured method, or the workflow is inactive while the production URL is called.",
      "fix_url": null,
      "fix_steps": "Confirm the caller uses the same HTTP method set in the Webhook node. Activate the workflow before using the /webhook/ production URL (the /webhook-test/ URL only works with the canvas open and 'Listen for test event' clicked). After a path rename, deactivate, save, then reactivate to re-register.",
      "source_url": "https://community.n8n.io/t/webhook-error-the-requested-webhook-is-not-registered/15688",
      "source": "mined",
      "published": "",
      "id": "n8n-the-requested-webhook-is-not-registered"
    },
    {
      "error": "connect ECONNREFUSED 127.0.0.1:5432",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "connectivity",
      "cause": "The Postgres node cannot reach the database, typically because n8n is in Docker and the host is set to localhost/127.0.0.1 instead of the container name.",
      "fix_url": null,
      "fix_steps": "In Docker Compose, set the credential host to the Postgres service name (e.g. postgres), not localhost. Confirm port 5432 is exposed and pg_hba.conf/postgresql.conf allow remote connections from the n8n network. If using an SSH tunnel, upgrade to n8n v1.99.0 for the connection-pool fix.",
      "source_url": "https://community.n8n.io/t/postgres-node-connection-refused-error/82137",
      "source": "mined",
      "published": "",
      "id": "n8n-connect-econnrefused-127-0-0-1-5432"
    },
    {
      "error": "Unable to parse range: Sheet1!A:D1:undefined1",
      "platform": "n8n",
      "code": null,
      "versions": [
        "0.84.3"
      ],
      "category": "schema",
      "cause": "A regression in n8n v0.84.3 caused the Google Sheets Append operation to build malformed range strings with undefined suffixes.",
      "fix_url": null,
      "fix_steps": "Upgrade to n8n v0.84.4 or later which contains the patch. If you cannot upgrade immediately, replace the Append operation with a raw HTTP Request to the Sheets API using a correctly formed A1-notation range.",
      "source_url": "https://community.n8n.io/t/google-sheet-400-error-unable-to-parse-range/2427",
      "source": "mined",
      "published": "",
      "id": "n8n-unable-to-parse-range-sheet1-a-d1-undefined1"
    },
    {
      "error": "No columns found in Google Sheet. All rows will be appended",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "The Google Sheets node needs schema discovery at design time, but when the spreadsheet ID is a runtime expression it cannot read column headers during setup.",
      "fix_url": null,
      "fix_steps": "Pin sample data to the trigger so the Sheets node can resolve the expression and detect columns. Alternatively hard-code a representative spreadsheet ID during setup, load the schema, then switch the field back to an expression. Ensure the sheet has a populated header row in row 1.",
      "source_url": "https://community.n8n.io/t/google-sheets-append-or-update-row-fails-when-documentid-is-dynamic-columns-exist-at-runtime-but-not-in-setup/236727",
      "source": "mined",
      "published": "",
      "id": "n8n-no-columns-found-in-google-sheet-all-rows-will-be-appended"
    },
    {
      "error": "This model's maximum context length is 65536 tokens. However, you requested 73149 tokens.",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "The AI Agent/Chat Model node sends a request over the model's token limit, commonly because a shared Window Buffer Memory node accumulates all users' history under one session ID.",
      "fix_url": null,
      "fix_steps": "Set a unique session ID per user (e.g. {{ $json.subscriber_id }}). Reduce the memory node's 'Context Window Length' to 10-15 messages. Truncate or summarise large document content before the model call. Or switch to a larger-context model.",
      "source_url": "https://community.n8n.io/t/exceed-maximum-context-length/85711",
      "source": "mined",
      "published": "",
      "id": "n8n-this-model-s-maximum-context-length-is-65536-tokens-however-"
    },
    {
      "error": "Bad request, please check your parameters. Input tokens exceed the configured limits.",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "other",
      "cause": "The OpenAI node's memory accumulates history across users sharing one session ID, growing a single context window beyond the API token ceiling.",
      "fix_url": null,
      "fix_steps": "Assign a unique session ID per user (e.g. {{ $json.userId }}) in the memory node. Lower the history limit to 10-15 entries. Replace in-memory storage with an external DB (e.g. Supabase) for per-session isolation. Add a summarisation step if the payload itself is large.",
      "source_url": "https://community.n8n.io/t/bad-request-error-input-tokens-exceed-configured-limits-in-openai-node/273096",
      "source": "mined",
      "published": "",
      "id": "n8n-bad-request-please-check-your-parameters-input-tokens-exceed"
    },
    {
      "error": "Connection refused on SSH-tunnelled Postgres (127.0.0.1:34827)",
      "platform": "n8n",
      "code": null,
      "versions": [
        "1.78.1"
      ],
      "category": "connectivity",
      "cause": "n8n v1.78.1 introduced connection pooling with a hard maxConnections default that causes SSH-tunnelled Postgres connections to time out and refuse in looping workflows.",
      "fix_url": null,
      "fix_steps": "Upgrade to n8n v1.99.0 which contains the SSH-tunnel connection-pool fix. On earlier versions, raise the SSH tunnel idle timeout and reduce parallelism in loops that hit Postgres so the pool is not exhausted.",
      "source_url": "https://community.n8n.io/t/postgres-connection-refused-read-econnreset/60596",
      "source": "mined",
      "published": "",
      "id": "n8n-connection-refused-on-ssh-tunnelled-postgres-127-0-0-1-34827"
    },
    {
      "error": "There was an error initializing DB: relation \"credentials_entity\" does not exist",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "n8n's Postgres migrations run against the wrong schema when DB_POSTGRESDB_SCHEMA is set to anything other than 'public', leaving tables uncreated.",
      "fix_url": null,
      "fix_steps": "Set DB_POSTGRESDB_SCHEMA=public or remove the variable so n8n uses the default. If you need schema isolation, create it first and grant the user full privileges before starting n8n. After fixing, wipe the database and let n8n re-run migrations cleanly.",
      "source_url": "https://community.n8n.io/t/docker-there-was-an-error-initializing-db-relation-credentials-entity-does-not-exist/14157",
      "source": "mined",
      "published": "",
      "id": "n8n-there-was-an-error-initializing-db-relation-credentials-enti"
    },
    {
      "error": "function gen_random_uuid() does not exist",
      "platform": "n8n",
      "code": null,
      "versions": [
        "1.121.3"
      ],
      "category": "schema",
      "cause": "A migration calls gen_random_uuid(), which requires the pgcrypto extension, but that extension is absent on the Postgres database.",
      "fix_url": null,
      "fix_steps": "Connect as a superuser and run: CREATE EXTENSION IF NOT EXISTS pgcrypto; then restart n8n so the migration completes. For Kubernetes, add this to the postgres init script so it runs automatically on new clusters.",
      "source_url": "https://github.com/n8n-io/n8n-hosting/issues/54",
      "source": "mined",
      "published": "",
      "id": "n8n-function-gen-random-uuid-does-not-exist"
    },
    {
      "error": "There was an error running database migrations QueryFailedError: syntax error at or near \":\"",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "A previously interrupted migration left the migrations table inconsistent, so the next startup's migration runner emits a Postgres syntax error.",
      "fix_url": null,
      "fix_steps": "Export all workflows and credentials with the n8n CLI (n8n export:workflow --backup, n8n export:credentials --decrypted) first. Drop and recreate the database, let n8n run a clean migration, then re-import. Do not hand-patch the migrations table unless you know the exact failed step.",
      "source_url": "https://community.n8n.io/t/error-there-was-an-error-running-database-migrations-queryfailederror-syntax-error-at-or-near/31553",
      "source": "mined",
      "published": "",
      "id": "n8n-there-was-an-error-running-database-migrations-queryfaileder"
    },
    {
      "error": "cannot drop column role of table \"user\" because other objects depend on it",
      "platform": "n8n",
      "code": null,
      "versions": [
        "1.111.0"
      ],
      "category": "schema",
      "cause": "A migration tries to drop the legacy 'role' column but Postgres blocks the DROP because a constraint or index still references it, usually from a schema that diverged during an earlier upgrade.",
      "fix_url": null,
      "fix_steps": "Downgrade to the last working version before retrying the upgrade. Identify dependents with SELECT conname FROM pg_constraint WHERE conrelid='public.user'::regclass, drop them with ALTER TABLE public.user DROP CONSTRAINT <name>, then restart n8n to retry. Watch the GitHub issue for an official patch.",
      "source_url": "https://github.com/n8n-io/n8n/issues/19364",
      "source": "mined",
      "published": "",
      "id": "n8n-cannot-drop-column-role-of-table-user-because-other-objects-"
    },
    {
      "error": "SQLITE_BUSY: database is locked",
      "platform": "n8n",
      "code": "SQLITE_BUSY",
      "versions": [],
      "category": "config",
      "cause": "SQLite allows only one writer at a time; concurrent workflow executions writing simultaneously cause SQLITE_BUSY.",
      "fix_url": null,
      "fix_steps": "Migrate to PostgreSQL for any instance running concurrent workflows - SQLite is for single-user dev only. If migration must wait, set EXECUTIONS_PROCESS=main to serialise executions. On NAS/Azure file shares, move the SQLite file to local container storage (remote mounts have poor SQLite locking).",
      "source_url": "https://community.n8n.io/t/sqlite-busy-database-is-locked/7188",
      "source": "mined",
      "published": "",
      "id": "n8n-sqlite-busy-database-is-locked"
    },
    {
      "error": "Mismatching encryption keys. The encryption key in the settings file does not match the N8N_ENCRYPTION_KEY env var.",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "n8n auto-generated a random encryption key on first startup and stored it in ~/.n8n/config, but a different N8N_ENCRYPTION_KEY was later set in the environment.",
      "fix_url": null,
      "fix_steps": "Retrieve the original key from the container (docker exec -it <c> cat /home/node/.n8n/config) and set that exact value as N8N_ENCRYPTION_KEY in compose. To start fresh instead, remove containers and the data volume, then set the desired key before n8n first writes config. Never change the key after credentials are saved.",
      "source_url": "https://community.n8n.io/t/self-hosted-ai-starter-kit-error-message-mismatching-encryption-keys/56652",
      "source": "mined",
      "published": "",
      "id": "n8n-mismatching-encryption-keys-the-encryption-key-in-the-settin"
    },
    {
      "error": "Credentials could not be decrypted. The likely reason is that a different \"encryptionKey\" was used to encrypt the data.",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "A new container or recreated data volume started without the original N8N_ENCRYPTION_KEY, so n8n generated a new key that cannot decrypt existing credentials.",
      "fix_url": null,
      "fix_steps": "Always pin N8N_ENCRYPTION_KEY explicitly in compose before first startup and keep it across upgrades. If the original key is lost, credentials are unrecoverable - delete and recreate them. In queue mode, every main/worker/webhook container must share the identical key. Persist the /home/node/.n8n volume.",
      "source_url": "https://community.n8n.io/t/credentials-could-not-be-decrypted-the-likely-reason-is-that-a-different-encryptionkey-was-used-to-encrypt-the-data-docker/158793",
      "source": "mined",
      "published": "",
      "id": "n8n-credentials-could-not-be-decrypted-the-likely-reason-is-that"
    },
    {
      "error": "Missing encryption key. Worker started without the required N8N_ENCRYPTION_KEY",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "In queue mode, worker containers must have N8N_ENCRYPTION_KEY set explicitly; they do not read the main instance's config file.",
      "fix_url": null,
      "fix_steps": "Add N8N_ENCRYPTION_KEY=<same value as main> to every worker service in compose. Retrieve it from the main instance if not set explicitly (docker exec <main> cat /home/node/.n8n/config). Restart workers. If using N8N_ENCRYPTION_KEY_FILE, read the file in an entrypoint and export it as N8N_ENCRYPTION_KEY due to a known bug.",
      "source_url": "https://community.n8n.io/t/n8n-worker-get-error-n8n-encryption-key-var-after-update-new-version/35878",
      "source": "mined",
      "published": "",
      "id": "n8n-missing-encryption-key-worker-started-without-the-required-n"
    },
    {
      "error": "Unable to connect to Redis after trying to connect for 10s",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "connectivity",
      "cause": "The n8n main/worker cannot reach Redis, commonly from an incorrect QUEUE_BULL_REDIS_HOST, a Docker network mismatch, or TLS issues.",
      "fix_url": null,
      "fix_steps": "Verify QUEUE_BULL_REDIS_HOST/PORT match the Redis service name and port and that both containers share a network. For TLS Redis, mount the CA cert and set QUEUE_BULL_REDIS_TLS=true with cert paths. If Redis has idle timeouts, set QUEUE_BULL_REDIS_TIMEOUT_THRESHOLD below the server timeout to reconnect proactively.",
      "source_url": "https://community.n8n.io/t/n8n-queue-mode-with-redis-and-self-signed-certificates/61046",
      "source": "mined",
      "published": "",
      "id": "n8n-unable-to-connect-to-redis-after-trying-to-connect-for-10s"
    },
    {
      "error": "All executions stuck in \"Queued\" / \"Starting soon\" and never executed",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "Workers disconnected from Redis (or never started) while holding job locks, leaving queued executions in a stale locked state that new workers cannot claim.",
      "fix_url": null,
      "fix_steps": "Set QUEUE_HEALTH_CHECK_ACTIVE=true to detect worker disconnects. Restart worker containers to release stale Redis locks; jobs requeue automatically. Ensure every main/webhook/worker container shares EXECUTIONS_MODE=queue and identical Redis vars. Avoid OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=true if you stop executions manually.",
      "source_url": "https://community.n8n.io/t/urgent-all-executions-stuck-in-queued-queue-mode-redis-stack-review-request/225804",
      "source": "mined",
      "published": "",
      "id": "n8n-all-executions-stuck-in-queued-starting-soon-and-never-execu"
    },
    {
      "error": "Connection Lost (workflow editor, behind nginx reverse proxy)",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "config",
      "cause": "The nginx location block is missing the WebSocket upgrade headers, so the push/SSE channel n8n uses for editor live-updates is dropped by the proxy.",
      "fix_url": null,
      "fix_steps": "Add to the n8n location block: proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection \"upgrade\"; Also set proxy_set_header Host $host; and X-Forwarded-Proto $scheme;. Reload nginx and hard-refresh the browser.",
      "source_url": "https://community.n8n.io/t/connection-lost-using-nginx-reverse-proxy-n8n-1-16/32962",
      "source": "mined",
      "published": "",
      "id": "n8n-connection-lost-workflow-editor-behind-nginx-reverse-proxy"
    },
    {
      "error": "read ECONNRESET",
      "platform": "n8n",
      "code": "ECONNRESET",
      "versions": [],
      "category": "connectivity",
      "cause": "The remote server abruptly closed the TCP connection mid-transfer, often due to firewall rules, TLS mismatches, keep-alive timeouts, or the n8n host lacking a stable outbound IP on the target's allowlist.",
      "fix_url": null,
      "fix_steps": "Retry the request to rule out a transient blip, then confirm your n8n host's outbound IP is not blocked or rate-limited by the target. In Docker, ensure a stable network route (not NAT hairpin). Enable 'Retry on Fail' on the HTTP Request node (3 retries, 1s wait); for SFTP, downgrading ssh2-sftp-client to 10.x has resolved it.",
      "source_url": "https://community.n8n.io/t/http-post-request-error-read-econnreset/22839",
      "source": "mined",
      "published": "",
      "id": "n8n-read-econnreset"
    },
    {
      "error": "connect ETIMEDOUT",
      "platform": "n8n",
      "code": "ETIMEDOUT",
      "versions": [],
      "category": "timeout",
      "cause": "The outbound TCP connection to the target host got no reply within the OS connect timeout, usually because the destination is firewalled or unreachable from the n8n network.",
      "fix_url": null,
      "fix_steps": "Verify the endpoint is reachable from the n8n host (curl/wget from the same container). Check cloud security-group/firewall rules for the destination port. In Docker, confirm the container can reach external IPs. Enable 'Retry on Fail' as a short-term mitigation while the network path is fixed.",
      "source_url": "https://community.n8n.io/t/my-http-request-node-to-an-api-keeps-failing-with-etimedout/178585",
      "source": "mined",
      "published": "",
      "id": "n8n-connect-etimedout"
    },
    {
      "error": "getaddrinfo EAI_AGAIN",
      "platform": "n8n",
      "code": "EAI_AGAIN",
      "versions": [],
      "category": "connectivity",
      "cause": "DNS resolution returned a temporary failure, most often because n8n runs in an Alpine/musl Docker image whose DNS resolver is less resilient than glibc, or the container's DNS server is overwhelmed.",
      "fix_url": null,
      "fix_steps": "Add '--dns 8.8.8.8 --dns 1.1.1.1' to docker run (or 'dns:' in compose) to use reliable resolvers. If you build the image, switch from Alpine to a Debian/Ubuntu base. Enable 'Retry on Fail' as a stopgap; on n8n Cloud it is usually transient and re-running after ~2 minutes succeeds.",
      "source_url": "https://community.n8n.io/t/getaddrinfo-eai-again-dns-error/33064",
      "source": "mined",
      "published": "",
      "id": "n8n-getaddrinfo-eai-again"
    },
    {
      "error": "HTTP Request: Credentials not found",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "The credential referenced by the node was created by a different user account; on Community Edition each credential is private to its creator.",
      "fix_url": null,
      "fix_steps": "Open the node, click the credential selector, and create a fresh credential under your own account instead of reusing another user's. Re-enter all credentials after importing a workflow. Teams needing shared credentials should use a plan that supports credential sharing.",
      "source_url": "https://community.n8n.io/t/error-http-request-throws-credentials-not-found-error/229864",
      "source": "mined",
      "published": "",
      "id": "n8n-http-request-credentials-not-found"
    },
    {
      "error": "Node has no access to credential",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "auth",
      "cause": "A workflow was exported from one instance/user and imported into another; the credential IDs in the JSON no longer match any credential on the new instance.",
      "fix_url": null,
      "fix_steps": "After importing, open every flagged node and re-select or recreate the credential from the dropdown — do not copy credential IDs across instances. For multi-instance setups, export credentials with 'n8n export:credentials' and import them on the target before importing workflows.",
      "source_url": "https://community.n8n.io/t/error-node-has-no-access-to-credential/35780",
      "source": "mined",
      "published": "",
      "id": "n8n-node-has-no-access-to-credential"
    },
    {
      "error": "502 Bad Gateway (self-hosted, behind reverse proxy)",
      "platform": "n8n",
      "code": "502",
      "versions": [],
      "category": "config",
      "cause": "The reverse proxy (nginx/Caddy) closes the upstream connection before a long-running execution completes, because the default proxy_read_timeout of 60s is too short.",
      "fix_url": null,
      "fix_steps": "Set 'proxy_read_timeout 300s; proxy_connect_timeout 300s; proxy_send_timeout 300s;' in the nginx server block and reload. Add WebSocket upgrade headers to prevent editor disconnects. Under load, move from SQLite to PostgreSQL and consider EXECUTIONS_MODE=queue with Redis.",
      "source_url": "https://community.n8n.io/t/self-hosted-n8n-on-hostinger-vps-frequent-502-bad-gateway-errors-server-hangs-during-workflow-execution/274581",
      "source": "mined",
      "published": "",
      "id": "n8n-502-bad-gateway-self-hosted-behind-reverse-proxy"
    },
    {
      "error": "The workflow did not return a response",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "An AI Agent sub-workflow tool ran but the parent got no structured output, typically because parallel branches converge without a Merge node and a race drops the final item.",
      "fix_url": null,
      "fix_steps": "Insert a Merge node (Combine) before the sub-workflow's final node to consolidate branches. Ensure the last node emits a JSON object with a 'response' key. For webhook sub-workflows, add a 'Respond to Webhook' node set to 'First incoming Item'. Test the sub-workflow in isolation first.",
      "source_url": "https://community.n8n.io/t/ai-agent-sub-workflow-tool-the-workflow-did-not-return-a-response/129345",
      "source": "mined",
      "published": "",
      "id": "n8n-the-workflow-did-not-return-a-response"
    },
    {
      "error": "Can't get data for expression - Missing pairedItem data",
      "platform": "n8n",
      "code": null,
      "versions": [],
      "category": "schema",
      "cause": "A Code node did not attach paired-item metadata to its output, so downstream expressions like $('Node').item cannot trace which input produced each output.",
      "fix_url": null,
      "fix_steps": "Return items with a 'pairedItem' index, e.g. return items.map((item, i) => ({ json: item.json, pairedItem: i })). See the n8n docs 'Item linking in the Code node'. For single items use $input.first() instead of .item. Re-run from the start, not mid-execution.",
      "source_url": "https://community.n8n.io/t/error-can-t-get-data-for-expression/33344",
      "source": "mined",
      "published": "",
      "id": "n8n-can-t-get-data-for-expression-missing-paireditem-data"
    }
  ]
}