m Yosh moved page ProtoFlux:Start ASync Task to ProtoFlux:Start Async Task: ASync -> Async |
no async context |
||
| Line 14: | Line 14: | ||
|}} | |}} | ||
The '''Start Async Task''' node starts a new | The '''Start Async Task''' node starts a new [[ExecutionContext]] using [[async flow]] at the current impulse. | ||
== Inputs == | == Inputs == | ||
| Line 26: | Line 26: | ||
=== TaskStart ([[Impulses#ASync|AsyncResumption]]) === | === TaskStart ([[Impulses#ASync|AsyncResumption]]) === | ||
The new | The new ExecutionContext made by the node. This impulse chain is [[async]] and will run until it encounters any sort of delay, at which it will continue execution along the <code>OnStarted</code> chain and follow standard sync/async flow. | ||
The context made by this node is ''nested'', meaning that any context-specific things, such as [[ProtoFlux:Local|locals]], are duplicated from the context that <code>*</code> comes from. Any future changes to context-specific things will not be reflected in the <code>OnStarted</code> chain and vice versa. | |||
=== OnStarted ([[Impulses|Continuation]]) === | === OnStarted ([[Impulses|Continuation]]) === | ||
| Line 36: | Line 36: | ||
=== OnFailed ([[Impulses|Continuation]]) === | === OnFailed ([[Impulses|Continuation]]) === | ||
Fires if the task was unable to be started. | Fires if the task was unable to be started. This only fires if <code>TaskStart</code> is not connected to any node. | ||
== See Also == | |||
* [[Impulses#Async]] for more information about async flow. | |||
* [[ExecutionContext]] for more information about the context this node creates. | |||
[[Category:ProtoFlux:Flow:Async]] | [[Category:ProtoFlux:Flow:Async]] | ||
Latest revision as of 20:52, 29 January 2025
The Start Async Task node starts a new ExecutionContext using async flow at the current impulse.
Inputs
* (Call)
Start the async task.
Outputs
TaskStart (AsyncResumption)
The new ExecutionContext made by the node. This impulse chain is async and will run until it encounters any sort of delay, at which it will continue execution along the OnStarted chain and follow standard sync/async flow.
The context made by this node is nested, meaning that any context-specific things, such as locals, are duplicated from the context that * comes from. Any future changes to context-specific things will not be reflected in the OnStarted chain and vice versa.
OnStarted (Continuation)
Fires once TaskStart encounters any sort of delay, effectively running at the same time given the now-separate contexts.
OnFailed (Continuation)
Fires if the task was unable to be started. This only fires if TaskStart is not connected to any node.
See Also
- Impulses#Async for more information about async flow.
- ExecutionContext for more information about the context this node creates.