@ancient-wolf-19325 explain Traces in Flyte V2

Traces in Flyte V2 provide fine-grained observability and resumption capabilities for functions within workflows. By using the

@flyte.trace

decorator on helper functions, Flyte captures execution details, creates checkpoints for resumption, and enables efficient recovery from failures. Traces work only within task execution contexts and are primarily used for tracking API calls, data processing, or computations inside tasks, not for the tasks themselves. Errors are not recorded in traces—only successful executions are checkpointed and can be resumed after failure. Traces support async, sync (coming soon), and generator functions, and integrate with task-level caching for efficient workflow execution and recovery. For more, see the Flyte V2 Traces documentation. Would you like more detail or code examples? Sources: - Traces | Flyte V2 User Guide 👍 1 button 👎 0 button 💡 Hint: Mention @ancient-wolf-19325 in the thread for followups.