Apply feedback

Author: Carey MacDonald

articles/search/cognitive-search-common-errors-warnings.md

@@ -50,10 +50,11 @@ Indexer read the document from the data source, but there was an issue convertin
 | Could not read field value | Could not read the value of column `'fieldName'` at index `'fieldIndex'`. A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) | These errors are typically due to unexpected connectivity issues with the data source's underlying service. Try running the document through your indexer again later. |
 
 ### Skill input 'languageCode' has the following language codes 'X,Y,Z', at least one of which is invalid.
+One or more of the values passed into the optional `languageCode` input of a downstream skill is not supported. This can occur if you are passing the output of the [LanguageDetectionSkill](cognitive-search-skill-language-detection.md) to subsequent skills, and the output consists of more languages than are supported in those downstream skills.
 
-This error means that one of the values passed into the optional `languageCode` input of the skill is invalid for that skill. If you are opting to pass the output of the [LanguageDetectionSkill](cognitive-search-skill-language-detection.md) into each of your subsequent skills, this may be causing issues as the output of the [LanguageDetectionSkill](cognitive-search-skill-language-detection.md) is a larger set of languages than is supported for the other text based skills. If you know that your data set is all in one language, you can remove the [LanguageDetectionSkill](cognitive-search-skill-language-detection.md) and the `languageCode` skill input and use the `defaultLanguageCode` skill parameter for that skill instead. Please note that that language must still be supported for that skill type for this to work as expected.
+If you know that your data set is all in one language, you should remove the [LanguageDetectionSkill](cognitive-search-skill-language-detection.md) and the `languageCode` skill input and use the `defaultLanguageCode` skill parameter for that skill instead, assuming the language is supported for that skill.
 
-If you know that your data set contains multiple languages and thus you need the [LanguageDetectionSkill](cognitive-search-skill-language-detection.md) and `languageCode` input, consider adding a [ConditionalSkill](cognitive-search-skill-conditional.md) to filter out the text with languages that are not supported before passing in the text to the skill in question.  Here is an example of what this might look like for the EntityRecognitionSkill:
+If you know that your data set contains multiple languages and thus you need the [LanguageDetectionSkill](cognitive-search-skill-language-detection.md) and `languageCode` input, consider adding a [ConditionalSkill](cognitive-search-skill-conditional.md) to filter out the text with languages that are not supported before passing in the text to the downstream skill.  Here is an example of what this might look like for the EntityRecognitionSkill:
 
 ```json
 {
@@ -77,7 +78,7 @@ Here are some references for the currently supported languages for each of the s
 There are two cases under which you may encounter this error message, each of which should be treated differently. Please follow the instructions below depending on what skill returned this error for you.
 
 #### Built-in Cognitive Service skills
-Many of the built-in cognitive skills, such as language detection, entity recognition, or OCR, are backed by a Cognitive Service web api endpoint.  Sometimes, there are transient issues with these endpoints that may cause requests to not return in a reasonable amount of time. There is no action for you as the user to take except to wait for a period of time in order to allow for the transient issue to be resolved. Consider [setting your indexer to run on a schedule](search-howto-schedule-indexers.md) if you haven't already, and likely the next time the indexer is scheduled to execute the transient issue will be resolved and the indexer will be able to continue making progress.
+Many of the built-in cognitive skills, such as language detection, entity recognition, or OCR, are backed by a Cognitive Service API endpoint. Sometimes there are transient issues with these endpoints and a request will time out. For transient issues, there is no remedy except to wait and try again. As a mitigation, consider setting your indexer to [run on a schedule](search-howto-schedule-indexers.md). Scheduled indexing picks up where it left off. Assuming transient issues are resolved, indexing and cognitive skill processing should be able to continue on the next scheduled run.
 
 #### Custom skills
 If you encounter a timeout error with a custom skill you have created, there are a couple of things you can try. First, review your custom skill and ensure that it is not getting stuck in an infinite loop and that it is returning a result consistently. Once you have confirmed that is the case, determine what the execution time of your skill is. If you didn't explicitly set a `timeout` value on your custom skill definition, then the default `timeout` is 30 seconds. If 30 seconds is not long enough for your skill to execute, you may specify a higher `timeout` value on your custom skill definition. Here is an example of a custom skill definition where the timeout is set to 90 seconds: