This page details some frequently asked questions about the AIP Logic application.
Review the documentation on how to use a Logic function.
All activity in AIP Logic counts toward token limits, including tool responses. Token limits reset on a per-block basis. You can see the number of tokens used at the end of each message in the Debugger. If the bar is red, consider reducing your token count to facilitate reliable performance.
We recommend the following steps to reduce your token count:
OBJECT_NAME property1 property2 etc.) that the LLM sends and receives; you can see this in the Debugger by selecting Show raw.A single large block allows you to iterate quickly and easily make large changes while experimenting with the LLM's capabilities, but you might want to split your Logic into multiple blocks if:
Since each block gets its own context window, splitting into multiple blocks can have the following advantages:
To improve the performance of an AIP Logic block, try the following suggestions:
You can modify the temperature of the LLM, a parameter that represents the randomness of an LLM’s response, by editing the temperature in a Use LLM block's Configuration text field. The default temperature is 0. Lower temperatures return a more deterministic output.
Example code:
Copied!1 2 3{ "temperature": 0.9 }
Yes, you can currently add a tool that allows Logic to perform semantic search on the Ontology, made possible either through an action or writing a function-on-object which is then called from AIP Logic. Review the semantic search workflow tutorial to learn more.
You can help an LLM “learn” from feedback with this design pattern, if it suits your workflow:
Add unit tests to check whether the function runs successfully on a given input. You can also use AIP Evals to create evaluation suites for your Logic functions. To generate a suite, open the Evals tab in the right sidebar and select Generate evals. AIP Evals bootstraps the suite with test cases, evaluators, and metrics based on your function. Review and refine the generated test cases and evaluators before running evaluations. The Results view includes a built-in results analyzer that clusters failing cases into root-cause categories, surfaces representative examples, and proposes targeted prompt changes to improve accuracy. Learn more in AIP Evals: Getting started.
In Run history, use Add as test case to convert historical execution results into test cases for new or existing evaluation suites. This helps you build comprehensive test suites from function executions.
Yes, you can see and rollback to previously saved versions using the version history sidebar.
Select a prior version from the list to compare with the current state.

Yes. By using the "Struct" output type you can return multiple named values.

Yes, when you add an Object Query tool on a Function tool in the LLM block, you can select Configure object return limits to choose the number of objects you would like to return from any tool use.

While testing and developing your AIP Logic function in the Debugger, the function is not subject to the five-minute execution time limit. However, when the function is called from either the Workshop environment or through the function execution API, the five-minute execution time limit is enforced.