From 1956cf6d0459f2fa7d9b99379882927bda55c398 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ey=C3=BE=C3=B3r=20Magn=C3=BAsson?= Date: Wed, 1 Apr 2020 10:29:24 +0200 Subject: [PATCH] docs: fix type --- docs/misc/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/misc/faq.md b/docs/misc/faq.md index 79d28fa61c..42ada6ae36 100644 --- a/docs/misc/faq.md +++ b/docs/misc/faq.md @@ -139,7 +139,7 @@ It is, which is why we recommend that tasks are written to be idempotent. Tasks This is intentional, we don't re-run tasks on file watch events. We debated this behavior quite a bit and ultimately opted not to run task dependencies on every watch event. -### Why is my task not running on `garden deploy` or `garden env`? +### Why is my task not running on `garden deploy` or `garden dev`? The task result is likely cached. Garden won't run tasks with cached results unless `cacheResult: false` is set on the task definition.