Pedro Machado
03/10/2022, 4:26 PMNo heartbeat detected from the remote task; retrying the run.This will be retry 1 of 2.
However, the last message was written 12 hours ago. It does not look like the flow got retried at all.
Could someone help me figure out what may have happened? I am using ECS to run the flows.
The flow run is fed29ba9-66a6-4f0b-aa69-cf9db908bd58
I went ahead and canceled it but it does not offer me the option to restart it. How can I restart it and preserve the same flow run ID so that the tasks that succeeded are not executed again? Ideally, I'd rely on the task state but if they need to run again, I am hoping that caching will help avoid doing the work again. The cache key is based on the flow_run_id
.
Thanks!Kevin Kho
03/10/2022, 4:29 PMPedro Machado
03/10/2022, 4:47 PMtargets
based on the flow_run_id
and map index.
The only issue would be that I am using today
as well and this ran last night:
target="prefect-results/employee_profiles/"
"{refresh-mode}/{today}/{flow_run_id}_{map_index}.json",
Assuming that I work around the date issue, could I just set the flow run to scheduled
? Would it take advantage of caching?Kevin Kho
03/10/2022, 4:58 PMPedro Machado
03/10/2022, 5:09 PM