Unity Async Strategy

Documentation only: no REST skills.

Scope: this module covers async code written into the Unity runtime (Update, coroutines, UniTask, cancellation, lifecycle ownership). It does not cover the REST protocol's own async jobs; for jobId polling see batch.

When to use

• Deciding how runtime work should be scheduled or cleaned up

Decision ladder

1. Ask first whether the task needs per-frame work at all.
2. If not, prefer events, callbacks, or explicit method calls.
3. For a short Unity-bound sequence, prefer a coroutine.
4. Recommend UniTask only when the project already uses it, or the user explicitly wants it and accepts the dependency.
5. Use Update only for true continuous simulation, polling, or input loops that cannot be event-driven.