Unverified50% confidenceFactExact time
The return value of a @task in the Functional API is recorded in the checkpoint; when resuming at the entry point, calls to already-completed tasks directly return the result from the checkpoint and skip the actual computation.
1
Sources
50%
Confidence
Long-term
Relevance
10/21/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe result returned by get_task contains an execution object that separates workflow information from runtime information.79% similarUnverifiedWhen the client actively aborts a call, the task has usually already finished executing on the server, and it should not be retried but rather retrieved by id; if there is no id, then list the tasks created by the current credentials.75% similarUnverifiedThe execution results of background tasks are not immediately returned to the model, but are injected into messages via task notifications before the next round of the main loop calls the model.75% similarUnverifiedThe caller specifies the target sub-workflow through the Execute Workflow node, and can pass structured input parameters and receive its returned results.69% similarUnverifiedUsing the /task shortcut command lets you view the full progress of background subagent tasks.68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1081288API
curl https://kongchang.com/api/v1/knowledge/claims/1081288MCP
get_claim(id=1081288)