Single Workflow Mode supports selecting specific workflow execution, using the designated workflow to respond to all user dialogues, ensuring business process integrity and standardization. It is suitable for enterprise service scenarios with clear business objectives and unified operation processes, such as standardized account opening or claim application processes in financial services, online appointment registration in the medical field, automated return processing in e-commerce after-sales, standardized government service handling (e.g., household registration modification), and manufacturing processes like work reporting and quality inspection tracking that require full adherence to preset steps and no deviation from the path for high-deterministic operations.
Invocation Method
Supports two invocation methods: synchronous call and asynchronous call. The webpage window provides only API call for testing. Actual usage requires calling the corresponding API to implement synchronous or asynchronous invocation.
Synchronous Call
Synchronous call runs the workflow in real time and replies to the user until the flow is completed before the next request can be triggered. For example, when calling the bank customer service workflow to implement credit card installment, the user needs to sequentially complete steps like selecting installment parameters and confirming the fee, then wait for real-time approval results. Only after this complete process can the user initiate a new request. When switching to Single Workflow Mode, it defaults to synchronous call.
Asynchronous Call
In synchronous call, users are required to wait in real time for the workflow to complete. If the workflow is complex and time-consuming, it may lead to execution timeout, ending the dialogue before the workflow finishes. For example, in a corporate multi-department joint review, if it times out, the user session will close in advance and the result cannot be obtained. If the caller is resource-constrained (such as a mobile terminal in a weak network environment) or unable to maintain a persistent connection (such as stateless HTTP requests), the execution result cannot be obtained in synchronous call. For instance, during cross-border approval, if the network is interrupted, the user interface will be unable to display the successful status of subsequent processing.
In this scenario, you can enable asynchronous call. After the workflow starts running, the user will get an immediate response and can then continue with other tasks without waiting for the task to complete. The task will execute separately in the backend. For example, when asynchronous calling a workflow for video analysis, the user will immediately receive a response confirming the task creation and can then exit the application or analyze the next video without a long delay for the task to complete.
Enabling Asynchronous Call
There are two ways to enable asynchronous call. You can switch to single workflow mode and select the workflow. If the workflow does not include interactive nodes, asynchronous call can be enabled.
Note:
Asynchronous call only supports single workflow applications excluding parameter extraction nodes, tab nodes, and reply nodes, performing asynchronous tasks without multi-turn interaction with users.
The concurrency of large model asynchronous calls is controlled by the permissions of that account. If multiple asynchronous call tasks are initiated simultaneously, queued waiting is required.
The task will return results within 24 hours.
Debug Method
Asynchronous calls support two debug methods: synchronous debug and asynchronous debug.
Synchronous Debug
In synchronous debug, the debug logic is the same as synchronous calls. Each step of the workflow (including external API invocation, waiting for messages, etc.) executes immediately, and users must wait for results before proceeding to the next task debugging. Task execution does not run in the background.
Asynchronous Debug
In asynchronous debug mode, the user inputs query in the dialog box to trigger an asynchronous invocation task once. After initiating the call, the page will show the task initiation status, task ID, creation time, input parameters, etc., and prompt the user to view the task execution result in "task result". The task proceeds to execute in the background, so there is no need to wait for the task to complete before proceeding to debug the next task.
Click "Asynchronous Task" to view the execution status of specific asynchronous tasks.
Click "Details" to view the specific workflow operating status and support Edit Workflow.
Other Configuration
Supports synonyms configuration, API parameters, application side user permission, and dialogue content review.
