AI and Rules - Recent Threads

RE: LLM execution failed: EVENT_NOT_FOUND - No event exists with name: setVariableValue

Aaron Appleman — Wed, 20 May 2026 19:32:23 GMT

I agree with this, make sure you are using a!map() and define your required input parameters as keys in the map object.

LLM execution failed: EVENT_NOT_FOUND - No event exists with name: setVariableValue

pradeepkumawat — Wed, 20 May 2026 08:26:03 GMT

I am facing error in the AI agend while reading the document.
LLM execution failed: EVENT_NOT_FOUND - No event exists with name: setVariableValue
Steps1: When I am passing this document as in the TOOL in the AI agend than it is working fine.
Steps2: When passing this document in the input than facing this issue.

Please just How can I pass document dynamically in the process model?

RE: LLM execution failed: EVENT_NOT_FOUND - No event exists with name: setVariableValue

Shubham Aware — Wed, 20 May 2026 09:36:45 GMT

Looks like input or output mapping is missing or mismatched.

Map the Agent input to a valid Document process variable in the process model.
Also map every output in the Agent node to a valid process variable with the correct type.

RE: AI Document Extraction

Preet Jain — Mon, 18 May 2026 21:14:04 GMT

Hi Kavya,

DocCenter should be able to help you pull out the additional handwritten text or notes if you add an extra field called "additional (handwritten) notes", set that field to use vision and provide some relevant business context.

If the handwritten note (meant for a certain field) is extending out of the box area, it should capture it automatically.

Does that answer your question?

Best,

Preet Jain

AI Document Extraction

Kavya — Sat, 16 May 2026 06:33:20 GMT

Hi Everyone,

We have a requirement where we are using AI-based document extraction to extract fields from a predefined form.

In the same form, if there are any empty spaces and the user accidentally adds handwritten text or notes outside the expected form fields, we need to detect that additional handwritten content separately.

Is it possible in Appian with help of AI extraction to achieve this use case ?

Kind Regards,

Kavya

RE: AI Document Extraction

Shubham Aware — Mon, 18 May 2026 06:04:46 GMT

It is possible to do at some extend using Unstructured Document Extraction. Prompt it to extract handwritten content separately from the form fields.

RE: AI Document Extraction

subhankar-Maantic — Mon, 18 May 2026 05:58:46 GMT

Consider a hybrid approach — Appian IDP for field extraction + Google/Azure AI for handwriting detection outside fields.

Few challenges

Coordinating responses from both and merging results in Appian adds complexity
Light pencil marks, stamps may be falsely detected as handwritten notes
Sending documents to external cloud AI services may violate data residency or compliance requirements depending on your policies

RE: AI Document Extraction

Stefan Helzle — Sat, 16 May 2026 09:52:00 GMT

I Think this should work, but suggest to test this. A language model can be told to treat handwriting separately, or any additional text outside fields. You will have to develop that prompt carefully.

RE: Smart Search Indexing Failure

Derek Knoderer — Thu, 30 Apr 2026 17:46:55 GMT

Hi James, of course. Ah, I see. Thanks for the clarification, and for requesting a support case be filed.

Smart Search Indexing Failure

jamesm4933 — Thu, 30 Apr 2026 16:20:13 GMT

I have a Record Type with a Document record field. We have a business requirement to be able to use Smart/Semantic search on this and a text field.

The Smart Search Sync consistently fails with the following error message, and a list of failed record ids: "Cannot retrieve the document. Verify the document management record type is configured correctly."

Through investigation, we discovered, that the Document field for these records was NULL, which is consistent with the above error message.

We would like to have a successful search indexing, for this record type, and so we removed those records from the dataset temporarily. However, now we get the following error message: "We couldn't check the smart search status. Try resyncing your record type."

Attempting to Sync is what produced this error, so it seems a bit unhelpful as an error message.

Why is the indexing failing when the selected smart search field is empty? Is there a workaround?

Now that the Smart Search syncing is failing with no further information, what can we do?

RE: Smart Search Indexing Failure

jamesm4933 — Thu, 30 Apr 2026 17:43:49 GMT

Hi Derek, thanks for getting back to me. Maybe I could have been a little clearer. We DID in fact remove the rows without documents existing. This DID NOT result in indexing completing successfully. I will contact my management to request a support case be opened.

Thanks again.

RE: Smart Search Indexing Failure

Derek Knoderer — Thu, 30 Apr 2026 17:39:51 GMT

jamesm4933 Thank you for reporting this. Could you please file a forum support ticket for this issue?

We do have a known bug where document management record types with rows/records with null values for the document field cause an indexing error. We'll look at getting a bugfix for this prioritized soon.

As a temporary workaround, are you able to remove the rows without documents so that indexing can complete successfully? Or is there something about your use case that makes this unworkable?

We did not anticipate users having records for documents without any actual documents existing -- and would be interested to learn more about your use case/s for using document management record types in this way. Could you please provide this additional context as part of the support ticket? Sorry for any confusion or frustration this has caused you, and thank you for your understanding and assistance!

RE: AI Agent: INVALID_TOOL_RESPONSE

David G. — Fri, 17 Apr 2026 16:01:59 GMT

It seemed to be when generating the output record, if I remember correctly--was definitely always after most of the processing had been completed.

AI Agent: INVALID_TOOL_RESPONSE

David G. — Wed, 15 Apr 2026 19:19:59 GMT

Sometimes, when I test an agent, it processes for a while, then after a few minutes throws this error:

System Error

This appears to be a system issue. Try again later or submit a support case if the problem continues.

Source: Run Agent - Agent: DG_testAgent - Run ID: 52

Details: LLM execution failed: INVALID_TOOL_RESPONSE - Required schema field not provided in data tree: textValue

Any suggestions on what could be going on? Sometimes the agent succeeds, but the frequency of getting this error makes me concerned about using this in production.

26.3 environment hosted on Appian Cloud.

RE: AI Agent: INVALID_TOOL_RESPONSE

Sam Wahbeh — Fri, 17 Apr 2026 15:57:46 GMT

Hi David G.

Do you know if this is failing on the set variable call of the agent run or query record.

This error typically occurs when the LLM hallucinates and doesn't provide the expected schema for the tool call. We are looking at bumping up the number of retries in an upcoming version.

-Sam

RE: I am using a!currency to show thousand separator

shridevim9458 — Fri, 17 Apr 2026 14:11:47 GMT

Thank you so much.
This is the one I was looking for, it helped me.

I am using a!currency to show thousand separator

shridevim9458 — Fri, 17 Apr 2026 10:12:45 GMT

I am using a!currency to show thousand separator but it by default shows $ symbol if used USD ISO.Here I need to remove this $ symbol while displaying this field.

RE: I am using a!currency to show thousand separator

shridevim9458 — Fri, 17 Apr 2026 14:10:50 GMT

thank you so much...this will work.

Also I have tried Fixed() and this served the purpose without currency symbol.

RE: I am using a!currency to show thousand separator

Shubham Aware — Fri, 17 Apr 2026 12:38:43 GMT

Use fixed() instead of a!currency() if you only want commas and no $ symbol, because a!currency() is designed to display a currency indicator.

RE: I am using a!currency to show thousand separator

Harsha Sharma — Fri, 17 Apr 2026 12:27:38 GMT

Got it! You can strip away the US $ in this case then e. g.

stripwith(a!currency(isoCode: "USD",value:23546,indicatorAlignment: "START"),"US$")

RE: AI Agent: INVALID_TOOL_RESPONSE

Shubham Aware — Fri, 17 Apr 2026 12:04:37 GMT

I'm just trying to guess here, as this is new for us too, It’s probably the tool output schema, not the record-type final answer. The missing textValue error means one of the agent’s tool calls is returning data in a shape Appian doesn’t expect, so check the tool/record mapping and required fields first.

RE: I am using a!currency to show thousand separator

shridevim9458 — Fri, 17 Apr 2026 10:41:20 GMT

thanks for the reply...actually the display columns are number of packs so no need to have any currency symbol.

RE: I am using a!currency to show thousand separator

Harsha Sharma — Fri, 17 Apr 2026 10:25:11 GMT

Instead of $ would the code 'USD" work? like this

a!currency(
  isoCode: "USD",
  value: 1234.56,
  showSeparators: false,
  format: "CODE",
  indicatorAlignment: "START"
)

Using 'format' parameter you can show either $ or USD.

RE: AI Agent: INVALID_TOOL_RESPONSE

David G. — Thu, 16 Apr 2026 19:04:58 GMT

Not entirely sure which part you're suggesting for the fix. The agent's output is a record type, and I've given it explicit instructions about how to populate that. Are you suggesting to add a secondary output of type Text, with instructions along the lines of "If you run into any problems, just put a cry for help here"? Or are you instead suggesting that the problem's with one or more of the tools that I've given to the agent? In my current test, those tools are simply record types, which doesn't give me the opportunity for a "string fallback".

RE: AI Agent: INVALID_TOOL_RESPONSE

Shubham Aware — Thu, 16 Apr 2026 11:22:20 GMT

Most likely a bad/missing output field, the agent is expecting textValue - always provide a default string fallback.