Configuration errors
Configuration errors happen when product settings, flags, environment variables, or config files are invalid or inconsistent.
8451
Active Directory replication encountered a database errorActive Directory Replication
8606Active Directory replication failed because insufficient attributes were given to create an objectActive Directory Replication
8464Active Directory replication failed while syncing the partial attribute setActive Directory Replication
UnknownOperationExceptionAWS received an unknown or invalid operation nameGeneral
GITHUB_ENV cannot be used to set the NODE_OPTIONS environment variableGitHub Actions blocks NODE_OPTIONS from being set through GITHUB_ENVGitHub Actions
Wrapping with double quotes (") will throw an errorGitHub Actions expression string used double quotes and failedGitHub Actions
`!` is reserved notation in YAML formatGitHub Actions if expression starting with ! failed YAML parsingGitHub Actions
on.workflow_call.inputs.<input_id>.typeGitHub Actions reusable workflow input is missing a required typeGitHub Actions
Subdirectories of the workflows directory are not supportedGitHub Actions reusable workflow is in an unsupported directoryGitHub Actions
For a workflow to be reusable, the values for `on` must include `workflow_call`GitHub Actions reusable workflow is missing workflow_callGitHub Actions
If a caller workflow passes an input that is not specified in the called workflow, this results in an error.GitHub Actions reusable workflow received an undeclared inputGitHub Actions
You cannot use contexts or expressions in this keywordGitHub Actions reusable workflow uses does not allow contexts or expressionsGitHub Actions
Skip output `{output.Key}` since it may contain secretGitHub Actions skipped a job output because it may contain a secretGitHub Actions
Every step must define a `uses` or `run` keyGitHub Actions step is missing run or usesGitHub Actions
Invalid - creates a parse error that prevents your workflow from runningGitHub Actions workflow failed because a special pattern was not quotedGitHub Actions
Workflow file parse errorGitHub Actions workflow YAML is invalidGitHub Actions
workflow_dispatch only triggers workflows that exist on the default branchGitHub Actions workflow_dispatch did not work because the workflow is not on the default branchGitHub Actions
Missing docs folderGitHub Pages build failed because the docs folder is missingGitHub Pages
Missing submoduleGitHub Pages failed because a referenced submodule is missingGitHub Pages
Relative permalinks configuredGitHub Pages failed because relative permalinks are configuredGitHub Pages
Invalid submoduleGitHub Pages failed because the submodule configuration is invalidGitHub Pages
Config file errorGitHub Pages failed with a Jekyll config file errorGitHub Pages
Invalid YAML in data fileGitHub Pages Jekyll build failed because a data file contains invalid YAMLGitHub Pages
405 Method Not AllowedHTTP 405 Method Not AllowedHTTP Status Codes
409 ConflictHTTP 409 ConflictHTTP Status Codes
AADSTS650056Microsoft Entra rejected the app as misconfiguredMicrosoft Entra ID
AADSTS650057Microsoft Entra rejected the requested resource as invalid for the appMicrosoft Entra ID
AADSTS70011Microsoft Entra rejected the requested scope as invalidMicrosoft Entra ID
Invalid next.config.jsNext.js configuration contains invalid optionsNext.js
next.config.js Loading ErrorNext.js could not load next.config.jsNext.js
Invalid i18n configNext.js invalid i18n configurationNext.js
Invalid images configNext.js invalid images configurationNext.js
Invalid Layout or Page ExportNext.js invalid layout or page exportNext.js
Invalid use server valueNext.js invalid use server export valueNext.js
Invalid webpack resolve aliasNext.js invalid webpack resolve alias overrideNext.js
Built-in next/fontNext.js still using the deprecated @next/font packageNext.js
npm not running the latest version on a Windows machinenpm on Windows is not using the latest installed versionnpm
Could not open requirements filepip could not open the requirements filepip
Invalid requirementpip could not parse the requirement specifierpip
no Terraform configuration filesTerraform command ran without configuration files in the working directoryTerraform CLI
Unsupported argumentTerraform configuration contains an unsupported argumentTerraform CLI
Missing required argumentTerraform configuration is missing a required argumentTerraform CLI
Invalid function argumentTerraform could not convert the value to boolTerraform CLI
Invalid function argumentTerraform could not convert the value to numberTerraform CLI
Reference to undeclared local valueTerraform could not find the referenced local valueTerraform CLI
Invalid expressionTerraform could not parse the expressionTerraform CLI
CycleTerraform detected a dependency cycleTerraform CLI
Invalid "each" attributeTerraform each object does not contain the referenced attributeTerraform CLI
Unsupported block typeTerraform found a block type that is not expected hereTerraform CLI
Invalid characterTerraform found an invalid character in the configurationTerraform CLI
Invalid referenceTerraform found an invalid resource referenceTerraform CLI
Invalid function argumentTerraform one function received too many elementsTerraform CLI
Missing resource instance keyTerraform requires a specific resource instance keyTerraform CLI
React error #492The react package is not configured correctly for react-serverReact
This package is ESM only but it was tried to load by `require`Vite config loads an ESM-only package with requireVite