Skip to content

Commit 5dd4f92

Browse files
committed
Added several more missing anchors. Consistent line breaks and MD formatting pass
1 parent 2f329a7 commit 5dd4f92

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -103,13 +103,16 @@ While debugging this issue, be sure to pay attention to any [skill input warning
103103
<a name="could-not-execute-skill-because-web-api-skill-response-is-invalid"></a>
104104

105105
## `Error: Could not execute skill because Web API skill response is invalid`
106+
106107
The skill execution failed because the call to the Web API returned an invalid response. Typically, this class of failure occurs when custom skills are used, in which case you will need to debug your custom code to resolve the issue. If instead the failure is from a built-in skill, file a [support ticket](https://portal.azure.com/#create/Microsoft.Support) to get assistance.
107108

108109
<a name="skill-did-not-execute-within-the-time-limit"></a>
109110

110111
## `Error: Type of value has a mismatch with column type. Couldn't store in 'xyz' column. Expected type is 'abc'`
111112
If your data source has a field with a different data type than the field you're trying to map in your index, you may encounter this error. Check your data source field data types and make sure they are [mapped correctly to your index data types](/rest/api/searchservice/data-type-map-for-indexers-in-azure-search).
112113

114+
<a name="skill-did-not-execute-within-the-time-limit"></a>
115+
113116
## `Error: Skill did not execute within the time limit`
114117

115118
There are two cases under which you may encounter this error message, each of which should be treated differently. Follow the instructions below depending on what skill returned this error for you.
@@ -167,6 +170,7 @@ The document was read and processed, but the indexer could not add it to the sea
167170
<a name="could-not-index-document-because-the-indexer-data-to-index-was-invalid"></a>
168171

169172
## `Error: Could not index document because some of the document's data was not valid`
173+
170174
The document was read and processed by the indexer, but due to a mismatch in the configuration of the index fields and the data extracted and processed by the indexer, it could not be added to the search index. This can happen due to:
171175

172176
| Reason | Details/Example

0 commit comments

Comments
 (0)