Hi I d like to confirm that using `task run id` as a target

Question

Hi I d like to confirm that using `task run id` as a target is a bug using 0 11 3 ```from prefect import task Flow from prefect engine results import LocalResult lcl res = LocalResult dir= ~ prefect guide results flow name task target= task name task run id def return list return 1 2 3 task target= task name map index prefect def mapped task x return x + 1 with Flow blah result=lcl res as flow mapped task map return list st = flow run flow visualize flow state=st ```

itay livni · Answer

Error ``` py37moc ilivni ilivni UX430UAR ~ prefect guide$ home ilivni miniconda3 envs py37moc bin python home ilivni prefect guide tst map py 0 11 3 2020 05 27 18 56 17 INFO prefect FlowRunner | Beginning Flow run for blah 2020 05 27 18 56 17 INFO prefect FlowRunner | Starting flow run 2020 05 27 18 56 17 INFO prefect TaskRunner | Task return list Starting task run 2020 05 27 18 56 17 ERROR prefect TaskRunner | Unexpected error KeyError task run id Traceback most recent call last File miniconda3 envs py37moc lib python3 7 site packages prefect engine runner py line 48 in inner new state = method self state args kwargs File miniconda3 envs py37moc lib python3 7 site packages prefect engine task runner py line 660 in check target if result exists target prefect context File home ilivni miniconda3 envs py37moc lib python3 7 site packages prefect engine results local result py line 123 in exists return os path exists os path join self dir location format kwargs KeyError task run id ```

nicholas · Answer

Hi < itay livni> would you mind opening an issue in GitHub and describing the behavior you re seeing there

itay livni · Answer

Will do

nicholas · Answer

Much appreciated smile

Chris White · Answer

We don t have a notion of `task run id` in Core only so that s the why we should find a way to not have a discrepancy between core cloud here

itay livni · Answer

Chris White · Answer

Thanks itay