From c78efe2f11b1b9b13314b1fc92ddd49caf57fe23 Mon Sep 17 00:00:00 2001 From: nate nowack Date: Fri, 31 Jan 2025 15:45:06 -0600 Subject: [PATCH] Update docs/v3/develop/task-caching.mdx --- docs/v3/develop/task-caching.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/v3/develop/task-caching.mdx b/docs/v3/develop/task-caching.mdx index 6bb5a43aa24b..21ac82e10e80 100644 --- a/docs/v3/develop/task-caching.mdx +++ b/docs/v3/develop/task-caching.mdx @@ -68,7 +68,7 @@ Prefect comes prepackaged with a few common cache policies: - `DEFAULT`: this cache policy uses the task's inputs, its code definition, as well as the prevailing flow run ID to compute the task's cache key. - `INPUTS`: this cache policy uses _only_ the task's inputs to compute the cache key. -- `TASK_SOURCE`: this cache policy uses _only_ the task's code definition (and **not** source code of nested tasks) to compute the cache key. +- `TASK_SOURCE`: this cache policy only considers raw lines of code in the task (and not the source code of nested tasks) to compute the cache key. - `FLOW_PARAMETERS`: this cache policy uses _only_ the parameter values provided to the parent flow run to compute the cache key. - `NO_CACHE`: this cache policy always returns `None` and therefore avoids caching and result persistence altogether.