Known Issues
This page explains the issues currently known to occur.
The content below includes issues that occur only under specific conditions.
In normal use, they do not affect every user.
Issues and Limitations by Feature
Notation Rules
- Ver.: The version in which the issue was introduced
Workflow
| No. | Ver. | Issue | Workaround |
|---|---|---|---|
| 1 | 1.0 | When GPT‑5.2 Instant is used in an AI step, an unnecessary string may be mixed into the end of the output, causing the subsequent JSON parsing to fail. | Use a model other than GPT‑5.2 Instant. |
| 2 | 1.0 | Even when a string type is specified for an input parameter, values with a leading zero (such as 0123, 0001, 01) lose the leading zero at runtime. | Add the following processing. 1. Before processing: add a prefix (0x) to the start of the string. 2. After it is treated as a string: remove the prefix. |
| 3 | 1.0 | In an agent call step, the actual content of the tool calls cannot be checked in the execution log. | Include an instruction to the agent to "output the name of the tool called, its parameters, and a summary of the result," and check the response message. Note: this is a summary output generated by the agent; the actual tool execution log cannot be checked. |
Tool Integration
| No. | Ver. | Integration Target | Issue | Details |
|---|---|---|---|---|
| 1 | 1.0 | Next Design | Requesting the list of a model's child entities may fail. | ■ |