Mark NS04/08/2023, 5:24 AM
then an error:
[WARNING] Task run 'bcc56e8e-a1bd-4145-abdb-aad866d63c6f' received abort during orchestration: The enclosing flow must be running to begin task execution. Task run is in PENDING state.
Previous advice has been that this is caused by an upstream problem, but I can't see anything in the logs (journalctl on ec2 instance) that would cause the enclosing flow to not be in a running state. Our infra is an prefect agent running on ec2, spawning docker containers on the same box. I checked the monitoring on the box - no cpu/mem spikes. I've added task retries, but I guess that's not going to fix it either, if the flow is already dead? What else should I look for?
[ERROR] prefect.exceptions.MissingResult: State data is missing. Typically, this occurs when result persistence is disabled and the state has been retrieved from the API.
Zanie04/10/2023, 3:05 PM
Mark NS04/10/2023, 3:31 PM
Zanie04/10/2023, 3:56 PM