Skip to content

Commit 9640115

Browse files
committed
clean up limitations/known issues page
1 parent deb4367 commit 9640115

File tree

1 file changed

+42
-36
lines changed

1 file changed

+42
-36
lines changed

solutions/search/agent-builder/limitations-known-issues.md

Lines changed: 42 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -14,47 +14,53 @@ These pages are currently hidden from the docs TOC and have `noindexed` meta hea
1414

1515
# Limitations and known issues in {{agent-builder}}
1616

17-
## Model selection
17+
## Limitations
1818

19-
Initially, {{agent-builder}} only supports working with the [Elastic Managed LLM](kibana://reference/connectors-kibana/elastic-managed-llm.md) running on the Elastic Inference Service, on {{ech}} and {{serverless-full}}.
19+
### {{agent-builder}} is not enabled by default
2020

21-
Locally this picks the first AI connector available.
21+
While in private technical preview, {{agent-builder}} is not enabled by default. Refer to [Get started](get-started.md#enable-agent-builder) for instructions.
22+
23+
### Model selection
24+
25+
Initially, {{agent-builder}} only supports working with the [Elastic Managed LLM](kibana://reference/connectors-kibana/elastic-managed-llm.md) running on the [Elastic Inference Service](/explore-analyze/elastic-inference/eis.md) {applies_to}`serverless: preview` {applies_to}`ess: preview 9.2`.
26+
27+
Learn about [pricing](https://www.elastic.co/pricing/serverless-search) for the Elastic Managed LLM.
2228

2329
## Known issues
2430

31+
### Default agent can misinterpret SQL syntax as ES|QL
32+
33+
The `.execute_esql` tool is designed only for [{{esql}}](elasticsearch://reference/query-languages/esql.md) syntax, not other query languages.
34+
35+
When using SQL syntax with the default agent, it attempts to use the `.execute_esql` tool instead of recognizing the input as SQL.
36+
37+
This results in parsing errors like this:
38+
```console-response
39+
[
40+
{
41+
"type": "error",
42+
"data": {
43+
"message": "parsing_exception\n\tCaused by:\n\t\tinput_mismatch_exception: null\n\tRoot causes:\n\t\tparsing_exception: line 1:15: mismatched input 'WHERE' expecting {<EOF>, '|', ',', 'metadata'}",
44+
"stack": "ResponseError: parsing_exception\n\tCaused by:\n\t\tinput_mismatch_exception: null\n\tRoot causes:\n\t\tparsing_exception: line 1:15: mismatched input 'WHERE' expecting {<EOF>, '|', ',', 'metadata'}\n at KibanaTransport._request (Desktop/Dev/kibana/node_modules/@elastic/elasticsearch/node_modules/@elastic/transport/src/Transport.ts:591:17)\n at processTicksAndRejections (node:internal/process/task_queues:105:5)\n at Desktop/Dev/kibana/node_modules/@elastic/elasticsearch/node_modules/@elastic/transport/src/Transport.ts:697:22\n at KibanaTransport.request (Desktop/Dev/kibana/node_modules/@elastic/elasticsearch/node_modules/@elastic/transport/src/Transport.ts:694:14)"
45+
}
46+
}
47+
]
48+
```
49+
50+
### Not all LLMs are compatible
51+
52+
While Elastic offers LLM connectors for many different vendors and models, not all LLMs are robust enough to be used with {{agent-builder}}.
53+
54+
The following errors suggest your selected model may not be compatible with {{agent-builder}}:
55+
56+
```console-response
57+
Error: Invalid function call syntax
58+
```
59+
60+
```console-response
61+
Error executing agent: No tool calls found in the response.
62+
```
2563

26-
- **Default agent can misinterpret SQL syntax as ES|QL**
27-
- The `.execute_esql` tool is designed only for [{{esql}}](elasticsearch://reference/query-languages/esql.md) syntax, not other query languages
28-
- When using SQL syntax with the default agent, it attempts to use the `.execute_esql` tool instead of recognizing the input as SQL
29-
- This results in parsing errors like this:
30-
```console-response
31-
[
32-
{
33-
"type": "error",
34-
"data": {
35-
"message": "parsing_exception\n\tCaused by:\n\t\tinput_mismatch_exception: null\n\tRoot causes:\n\t\tparsing_exception: line 1:15: mismatched input 'WHERE' expecting {<EOF>, '|', ',', 'metadata'}",
36-
"stack": "ResponseError: parsing_exception\n\tCaused by:\n\t\tinput_mismatch_exception: null\n\tRoot causes:\n\t\tparsing_exception: line 1:15: mismatched input 'WHERE' expecting {<EOF>, '|', ',', 'metadata'}\n at KibanaTransport._request (Desktop/Dev/kibana/node_modules/@elastic/elasticsearch/node_modules/@elastic/transport/src/Transport.ts:591:17)\n at processTicksAndRejections (node:internal/process/task_queues:105:5)\n at Desktop/Dev/kibana/node_modules/@elastic/elasticsearch/node_modules/@elastic/transport/src/Transport.ts:697:22\n at KibanaTransport.request (Desktop/Dev/kibana/node_modules/@elastic/elasticsearch/node_modules/@elastic/transport/src/Transport.ts:694:14)"
37-
}
38-
}
39-
]
40-
```
41-
42-
- **Not all LLMs are compatible**
43-
- While Elastic offers LLM connectors for many different vendors and models, not all LLMs are robust enough to be used with {{agent-builder}}.
44-
- Errors such as:
45-
```console-response
46-
Error: Invalid function call syntax
47-
```
48-
or
49-
```
50-
Error executing agent: No tool calls found in the response.
51-
```
52-
may indicate that your selected model is ill-equipped for the precise response structure necessary for {{agent-builder}}.
53-
- We recommend using the [Elastic Managed LLM](kibana://reference/connectors-kibana/elastic-managed-llm.md)
54-
55-
- **{{agent-builder}} is not accessible**
56-
- {{agent-builder}} was added in a private preview in September, 2025 for Serverless, and in 9.2.0 for Elastic Cloud.
57-
- While in this preview stage, {{agent-builder}} is not enabled by default.
58-
- To enable it, you must go to Stack Management -> Kibana -> Advanced Settings -> Elastic Agent Builder, and enable it.
64+
We recommend using the [Elastic Managed LLM](kibana://reference/connectors-kibana/elastic-managed-llm.md).
5965

6066

0 commit comments

Comments
 (0)