Hi everyone, I'm getting an error in all of my flows when running from Prefect Cloud. After ~9:50 mins (almost exactly) the execution of whatever task within the currently running subflow is running gets terminated. I see an error that's something like this:

Crash detected! Execution was cancelled by the runtime environment.

ERROR
Encountered exception during execution:
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 634, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 601, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1869, in _run_once
    event_list = self._selector.select(timeout)
  File "/usr/local/lib/python3.9/selectors.py", line 469, in select
    fd_event_list = self._selector.poll(timeout, max_ev)
  File "/usr/local/lib/python3.9/site-packages/prefect/engine.py", line 1613, in cancel_flow_run
    raise TerminationSignal(signal=signal.SIGTERM)
prefect.exceptions.TerminationSignal

The the subflow keeps running indefinitely despite having a failed task, and the main flow fails (its seems similar to https://github.com/PrefectHQ/prefect/issues/8481). This only seems to happen if the flow runs for 9 mins and 50 seconds, and it happens to whichever subflow/task is running at that time. Is there anything that might be causing this? Any help is greatly appreciated.

Hi, for some reason I am not seeing task inputs in the UI - see the images below. I am running the latest version of prefect (2.7.6)

Hi there, I want to use prefect for a small-scale personal project to automate a few python scripts. I was hoping to use a docker container with everything completely self-hosted (I am on Unraid OS) and see that prefect and prefect server are on dockerhub, but I see no actual documentation for using the dockerized version anywhere. When I pull the container down, as is, it fails to start and the only information I get in the log is the following:

|  __ \|  __ \|  ____|  ____|  ____/ ____|__   __|
           | |__) | |__) | |__  | |__  | |__ | |       | |
           |  ___/|  _  /|  __| |  __| |  __|| |       | |
           | |    | | \ \| |____| |    | |___| |____   | |
           |_|    |_|  \_\______|_|    |______\_____|  |_|

Thanks for using Prefect!!!

This is the official docker image for Prefect Core, intended for executing
Prefect Flows. For more information, please see the docs:
<https://docs.prefect.io/core/getting_started/quick-start.html>

Anyone have any idea of what I'm doing wrong? Should I be starting with prefect server instead?

Hi, I have a question about

apply_map

. Details following in the thread 🙂

@Marvin How can we pass environment variables to Prefect V3 from the worker start command? I have tried a .cmd script that sets the variable and boots the worker. I cannot access the variable via prefect.context.env, running a basic python script also does not see it. I must pass it with --env, but when I try use --env with Prefect Worker is will not boot due to unrecognised argument

@Marvin how can i get the task id of a task i'm serving? i want to trigger it from another process

@Marvin What are the best practices to manage different environments in Prefect Cloud?

@Marvin, when trying to serve an async flow, I keep getting an error about the event loop already running

@Marvin How to properly cleanup inside tasks when the flow receives a Cancellation signal?

@Marvin i am using a flow deployment method with GitRepository. The initial deployment was a success, which I think it is not a Git token or permission issue. However, once the remote git repository changes, I encounter this error.

subprocess.CalledProcessError: Command '['git', 'pull', 'origin', '--depth', '1']' returned non-zero exit status 128.