@Marvin I get this error on my flow:

received abort during orchestration: The enclosing flow must be running to begin task execution. Task run is in PENDING state

It seems like the error you're encountering might be related to a state management issue in the Prefect flow or task orchestration. The error message you provided indicates that the flow run is expected to be in a running state before task execution can begin, but the task run has remained in a PENDING state. This could be due to various reasons, such as orchestration logic errors or issues with the underlying infrastructure. There was a related discussion about this on a Prefect community Slack thread, but it doesn't appear to be directly addressing the root cause of your issue: Persistence Missing Result error - GitHub Issue #8228 Unfortunately, the thread doesn't provide a clear solution. Additionally, there's a pull request that could be related to logging improvements around this error: Add logs when task run receives abort signal and is in non-final state - PR #8097 Given that there isn't a clear solution available in the GitHub issues or pull requests, I recommend the following steps: 1. Ensure that your flow is properly started and that there aren't any environmental factors causing it to not enter the running state. 2. Verify your flow and task configuration to make sure that all prerequisites for running the tasks are met. 3. Make sure you have the right version of Prefect and any associated libraries that could be affecting this behavior. 4. If the problem persists, consider reaching out on the Prefect Slack community or creating a new GitHub issue to get more targeted help from the Prefect team. Please, keep an eye on the GitHub issues and pull requests for any updates or solutions that might be related to your problem.

thanks, but eventually it was related to K8s job block definition that was set to `job_watch_timeout_seconds=`600 seconds