No idea if this is a known issue. I can create a bug ticket if it is not.
If you have a Run action (a) that depends on a Run action (b) that depends on a Deploy action, and you’ve run all of these actions before, their statuses get cached so Garden doesn’t need to re-run them — all good so far. Then, if you delete and redeploy the Deploy action, I would want that to invalidate the previous run of both actions (b) and (a) but it does not. You can even force Run action (a) to run and it will error out (internally to the contents of the action, not a Garden error) because Garden will skip over (b) as having been run when in reality it has not been run against the new Deploy.