Aram Karapetyan

12/22/2022, 1:18 PM
hi, could someone advise on this issue?
11:57:28.377 | INFO    | prefect.engine - Engine execution of flow run
'ec6916a8-2d40-4ffb-9df3-cfb39f82c875' aborted by orchestrator: This run has
already terminated
No logs anywhere. Tasks/flows show as Crashed.

Mason Menges

12/22/2022, 9:32 PM
This particular message is part of an orchestration rule meant to prevent flows from being executed once they've already completed, it's likely this isn't the source of the crash itself. More likely you'll want to view the logs from the execution environment, assuming this is kubernetes if you can view the pod logs for the pod that was supposed to execute the job that might prove more insightful as to where the crash originated.

Aram Karapetyan

12/23/2022, 5:52 AM
Non get scheduled, that is the issue. We have one job scheduling others, and couple of seconds after new jobs scheduled most of them market as Crashed and I can see those logs and some other. Non related to application itself. Trying to chase each message.